Apple Pay
Accept Apple Pay payments from customers with Razorpay Curlec Checkout.
Apple Pay is a secure, contactless payment method that allows customers to pay using their Apple devices with Face ID/Touch ID authentication. Once Apple Pay is enabled and integrated, it appears on your Checkout page as a payment option, providing a frictionless checkout experience for customers. Know more about
.Feature Request
This is an on-demand feature. Please reach out to
to get this feature activated on your account.Integrating Apple Pay as a payment method on Checkout offers you the following advantages:
- Higher Conversion Rates: Up to 58% improvement in checkout conversion rates for customers.
- Reduced Friction: Eliminate manual card entry with biometric authentication (Face ID/Touch ID).
- Enhanced Security: Benefit from Apple's tokenisation and liability shift protection.
- Faster Checkout: 45% reduction in checkout time for Apple device users.
- Increased Average Order Value: Potential 12% increase in transaction value.
- Global Reach: Accept payments from customers in 70+ countries.
Before enabling Apple Pay, ensure you have:
- Razorpay Curlec Standard Checkout.
- HTTPS-enabled website with TLS 1.2 or higher.
- Access to your web server to upload verification files.
- Registered business entity (non-profit organisations are not eligible).
- Display the Apple Pay on your website in the payment methods section. Follow to display the Apple Pay brand mark to indicate support before checkout.
Follow the steps given below:
Apple Pay needs you to host a file in your domain.
Watch Out!
- The file path must be exactly as specified (case-sensitive).
- File hosting is required on websites where Razorpay Curlec Checkout loads as an overlay/iframe. This includes:
- WooCommerce, Magento and other ecommerce platforms where Razorpay Curlec appears as an overlay. Any website where
checkout.razorpay.comiframe is embedded.
- WooCommerce, Magento and other ecommerce platforms where Razorpay Curlec appears as an overlay. Any website where
- No file hosting required on:
- Shopify, Mobile SDKs (Flutter, Native iOS, React Native) and Razorpay Curlec no-code solutions, such as , and .
- File hosting is required if you use both hosted checkouts and overlay iframe integration (a non-Shopify website where an iframe loads as an overlay and Payment Buttons) on your business id. Please do not activate Apple Pay if you have both these kinds of checkouts unless you have hosted the file at the exact path.
-
Download the
. -
Host the file on your server.
- Upload the file to this exact path on your website:
/.well-known/apple-developer-merchantid-domain-association- For example, if your domain is
https://www.yourstorename.com, the file must be accessible at:
https://www.yourstorename.com/.well-known/apple-developer-merchantid-domain-association -
Ensure correct configuration. When setting up Apple Pay domain verification, follow these requirements:
File Path and Response
- The verification file must be accessible at the exact path,
/.well-known/apple-developer-merchantid-domain-association. - The file must return a direct HTTP 200 status code and not a 301, 302 or any 3xx redirects.
- Apple does not support HTTP URL redirects for the domain association file.
Server Configuration
- The file must be served via HTTPS 1.1 protocol.
- The file must have Content-Type: text/plain in the header.
- The file must be externally accessible (not behind authentication).
- The file must not be password protected.
- The file must not be behind a proxy or redirect.
Network Access
- Ensure the file is not behind a firewall or access restrictions.
- If using a firewall, configure it to allow Apple's .
- The verification file must be accessible at the exact path,
-
After completing the above steps, please contact the
to enable Apple Pay.
If you have uploaded the file or have not requested to opt out of Apple Pay, we will assume you are okay with
.Once domain verification is complete and terms are accepted:
- Apple Pay will automatically appear on your checkout when accessed by eligible customers.
- No code changes are required for Standard Checkout integration.
- The payment button displays dynamically based on device compatibility.
Given below is the payment flow for Apple Pay at Razorpay Curlec Checkout:
- The customer selects Apple Pay at checkout.

- Apple Pay displays their default card, billing address and the payment amount.
- They authenticate using Face ID, Touch ID or double-click the side button following the on-screen prompt Double Click to Pay.

- Upon successful authentication, the payment processes instantly and the customer is returned to your website or app with a confirmation.
If the Apple Pay button is not appearing, check for these common issues:
- Verify that your domain verification file is correctly hosted and accessible.
- Ensure your website is using HTTPS with proper TLS configuration.
- Confirm that international payments feature is enabled.
- Check if the customer's device supports Apple Pay.
Domain verification failures typically occur due to the following reasons:
- The verification file must return an HTTP 200 status code (not 301 or 302 redirects).
- The file path must be exactly
/.well-known/apple-developer-merchantid-domain-association. - The file must be accessible via HTTPS (not HTTP).
- The file content must exactly match what Razorpay Curlec provided, with no modifications or extra characters.
No code changes are required for Standard Checkout integration. Once domain verification is complete and Apple Pay is enabled on your account, it will automatically appear as a payment option for eligible customers.
There are no additional charges for Apple Pay transactions. Standard Razorpay Curlec payment processing rates apply, same as regular card transactions.
Apple Pay uses device-specific tokens that are automatically available for repeat purchases. Customers do not need to manually save payment details as their Apple Wallet handles this seamlessly.
Apple Pay transactions can be identified by checking the payment notes field in the API response or webhook payload:
"notes": {"provider": "apple_pay"}
This provider field will always contain apple_pay for Apple Pay transactions, making it easy to distinguish them from regular card payments.
There are structural differences between Apple Pay and standard card payment webhook events:
Apple Pay Payment:
"notes": {"provider": "apple_pay"}
Card Payment:
"notes": [],"token_id": "token_RIa2YPNM92wfzv"
Key differences:
- Apple Pay includes
provider: "apple_pay"in thenotesfield. - Card payments may include a
token_idfor saved cards.
Check if the file is hosted correctly at your domain by visiting:
https://www.yourstorename.com/.well-known/apple-developer-merchantid-domain-association.
Follow the
and ensure the file is publicly accessible.On Mobile:
- Open Safari in incognito mode on an iPhone with Apple Pay configured.
- Visit your checkout page.
- Apple Pay should appear at the top of payment options and under the cards menu.
On Desktop:
- Use Safari on macOS with Apple Pay configured.
- Ensure you are signed into your Apple account.
- Apple Pay will be visible if you have cards linked to your Apple account.
Was this page helpful?