Apple Pay
Apple Pay offers your customers a simple, secure, and private way to pay within your iOS and watchOS apps, and on your websites via Safari.
By integrating Apple Pay through BR-DGE, you'll not only deliver a smooth checkout experience but also gain greater control, flexibility, and reliability over your payment processes. This helps you optimize transaction routing, reduce declines, and strengthen fraud prevention, ultimately leading to increased conversion rates and new user adoption.
With features like Face ID, Touch ID, or a quick double-click on an Apple Watch, your customers can quickly and securely provide their payment details. This streamlined process eliminates manual entry, cutting down on friction and reducing cart abandonment.
How Apple Pay Works
The Apple Pay process is designed to be straightforward and secure, from the moment a user initiates a payment to the final authorization.
- Presenting the Button: In your app or on your website, first check if the user's device is capable of using Apple Pay and has a payment card set up. If so, display the Apple Pay button.
- Payment Sheet: When a user clicks the Apple Pay button, a payment sheet appears. This sheet, presented by PassKit (for apps) or Safari (for websites), displays the transaction details for the user to review. You specify the content of the payment sheet, such as shipping information and other line items, but should only request information essential for the transaction.
- User Authorization: The user authorizes the payment using Face ID, Touch ID, or by double-clicking their Apple Watch.
- Payment Token: Once authorized, your app or website receives an encrypted payment token. This token contains the necessary information to complete the transaction, including a device-specific account number (DPAN), the transaction amount, and a one-time-use cryptogram.
- Decryption and Authorization: The encrypted payment token can be used as a Payment Instrument in a BR-DGE Payment. BR-DGE will decrypt the payment token and route the payment to a processor of your choice.
On-boarding
Please contact support to enable Apple Pay on your retail channel(s). We offers two distinct on-boarding approaches depending on how you integrate with BR-DGE:
Option 1: On-boarding via the Apple Pay Web Merchant Registration API (For Hosted Payment Page & Web SDK)
This is the recommended approach for web integrations using our Hosted Payment Page or Web SDK, as it simplifies the setup process for merchants.
- How it works: We use our own Apple Developer account to on-board you through the Apple Pay Web Merchant Registration API.
- Benefits:
- Simplified setup for you.
- You do not need your own Apple Developer account subscription.
- All key and certificate management is handled by us.
- Limitations:
- This option is only available for web integrations via our Hosted Payment Page or Web SDK.
- It cannot be used for in-app integrations.
Option 2: On-boarding using your own Apple Developer account
This option is required if you want an in-app Apple Pay integration or a direct API integration for the web.
- How it works: You will use your own Apple Developer account to register a unique merchant identifier and set up your own cryptographic keys and certificates. We will provide a Certificate Signing Request (CSR) for you to upload to your Apple Developer portal. You then provide us with the resulting certificate from Apple which will allow us to decrypt your Apple Pay tokens.
- Benefits:
- Supports in-app integrations.
- You have complete control over the management of your certificates.
- Limitations:
- Requires you to have your own Apple Developer account.
Supported Channels | Limitations | Benefits | |
---|---|---|---|
Option 1 | Web (with BR-DGE Web SDK or Hosted Payment Page) | Cannot be used for in-app integrations, or direct integrations for Web. | Simplifies setup. No Apple Developer account needed for you. Key/certificate management handled by us. |
Option 2 | Web, App | You need your own Apple Developer account and unique merchant ID/keys/certificate setup. Will not work for hosted payment page integrations. | In-app integrations are supported. You have full control over certificate management. |
Integration Options
BR-DGE offers three distinct pathways for integrating Apple Pay, each designed to cater to different technical capabilities and business requirements. Your choice of integration will determine the level of control you have over the payment experience and the complexity of the implementation.
REST API
Enabling Apple Pay using the REST API gives you full control over your integration, using BR-DGE as your gateway. This method gives you full control of all aspects of the Apple Pay frontend.
Please refer to our REST API - Apple Pay page for more information on this integration method, and how to get started.
Web SDK
Our Web SDK Apple Pay module simplifies Apple Pay for Web. It streamlines your setup and centralizes payment management by using your existing BR-DGE Retail Channel configuration. Plus, it helps with merchant onboarding through the Apple Pay Web Merchant Registration API, so you don't need your own Apple Developer Account.
Key features include:
- Automatically showing or hiding the Apple Pay button based on device compatibility.
- Launching the Apple Pay Payment Sheet when needed.
- Customizing the Apple Pay Payment Sheet to accept only the cards configured for your BR-DGE Retail Channels. For example, if your Retail Channel is set up for Visa, Mastercard, and a local card network, but you only want to accept debit cards, the SDK will configure the sheet to reflect that.
To ensure Apple can confirm your ownership and control of the domains you will use for payment processing, you must verify these domains through BR-DGE. The BR-DGE customer support team will give you a file to place on each domain. This file needs to be publicly accessible, meaning it cannot be hidden behind proxies, require a login, nor redirect to another page. If you use a firewall to block internet traffic, you will need to add Apple IP addresses to your allowed list so Apple's servers can directly communicate with yours.
Apple does not support any other form of domain verification, such as using DNS records.
To keep your Apple Pay payments flowing smoothly, it's important that your domain's TLS certificate has a minimum of 30 days remaining before it expires. If the certificate does expire, Apple Pay transactions will be paused until a valid one is installed.
Hosted Payment Page (HPP)
As the BR-DGE Hosted Payment Page is a fully outsourced payment solution, enabling Apple Pay is much simpler than the other integration methods. To get started with Apple Pay via the BR-DGE Hosted Payment Page please get in contact with our support team.
Updated 5 days ago