One of the easiest things you should ever be able to do is give someone money for good and services. The same goes for being able to pay money in your pass, and with Apple Pay, you can do exactly that. Apply Pay is a secure system that allows coders to create a server managed payment system that collects end users payment information safely and makes transactions easy to do. The coding behind this is pretty straightforward, but does take a little bit of setup to get working properly.
The first thing you will need is a Merchant ID, and this can be done by going to the Member Center and looking in the Certificates section. From there, go to Identifiers and Profilers. In this section, you will see an option for Merchant IDs. Form here, just click add and fill in the necessary fields.
A merchant ID is needed by most online businesses to manage an online transaction account. In some ready-made apps, like Square, a Merchant ID is automatically assigned to an end user. Here, you are creating your own.
Once you have built your ID, make sure you go back and edit it to create a Certificate. This will help to authenticate your ID and make it so that you can accept payments and transfers. Also, remember to turn on the ability to work with Apple Pay in Xcode. You’ll have to go in and select Merchant IDs as the app tool you want to use, but you should only have to do this one time for your project.
Create a Payment Request
A payment request is how the user is able to make their payment. The request is something you code and customize, and when you do, you will need to consider overall important factors. First off, do you want the end user to be able to pay for certain items? Are you doing an item to item purchase, or would this be a bulk purchase with free add-ons? Each option must be explored in the code as you work. You will want to make a list of what should and should not be available to your end users before you begin.
Second, you will want to include authorizations for currency and region. Are you looking to only take money from the United States, or do you want to code for global payments? Beyond that, how are you tracking what Region of the globe the payment is coming from. To make your life easier, to avoid hassles with monetary exchange, and to help on your taxes, these are all things you will want to look at in the code. A simple request.currencycode line should be enough to set what you need, you just have to remember to do it.
Finally, remember to offer the end user a list of summary items. Think of how many times you’ve gone online shopping. When you’re done, you typically have a summary page to confirm your payments before processing your order. Don’t forget to offer users this important feature, as it can remove confusion about what they are doing and possibly make them want to order more products.
Now that you’re done with the payment, what about the shipping method? Listed in the code as a special payment summary item, having shipping options can be helpful and save you headaches. Giving users a set list of choices with the ability to customize and enter their own is not only useful, it’s expected of most online businesses.
This all means that you will have to collect not only the client’s billing information, but their shipping information as well. A request.merchantcapabilities line or two may be needed, as well as a request.requiredbillingaddressfields line. If you have to store separate blocks of code based on different shipping and billing, make sure you accommodate.
Finally, it wouldn’t hurt to add an additional notes field. After all, what if there are special shipping instructions for your products? Overall, there may be a bit you will have to research when it comes to setting up payment and shipping information, but the coding structure behind it is fairly straightforward, provide you remember each step and the appropriate coding lines.
Authorizing a payment comes down to completion blocks and if the user has hit all of the requirements. It’s really a giant if then clause, where the blocks must be filled in properly to accept the payment. The nice thing is you can set the code to delegate updates to shipping and cost. After all, different options toward the end can have an impact on how things are configured during the sale.
A proper payment can generate a payment token in the system. This token can be used by their code to reference the sale, and is specific to the sale in question. Think of it is a code receipt that you can later authorize or shoot down. All of this needs to be included, and some will take more time than others, but every line of code for your transactions needs to come down to whether or not the payment is accepted.
See Apple Pay Demo Here
If you’re looking for a more detailed walkthrough of the coding process behind accepting payments via Apple Pay, then check out this informative video from YouTube:
Also, be sure to do your homework. There are tons of free demos, coding examples, walkthroughs, and videos on how to work with Apple Pay and make it do what you need it to in your own custom environment.
Accepting money from clients shouldn’t be a hassle, and that goes for your coding team, too. Let Apple Pay make transactions via your apps a quick and easy process, and let your coders have the freedom of being able to work in a swift and open environment. With this freedom available, your coders will be able to focus on the rest of your app.