Acepta pagos con Apple Pay en tu integración con Kushki.Accept payments with Apple Pay in your Kushki integration. Depending on the type of solution you use (Smartlink/Button, Custom Integration, or Direct Integration with Apple Pay), the configuration process varies.
Important
🚧 BETA: Limited Availability 🇵🇪 🇨🇱 🇲🇽 🇨🇴 Please note that Apple Pay is currently in the Beta phase. This functionality is available only for merchants in Chile, Colombia, Mexico, and Peru, and it processes transactions exclusively with Visa and Mastercard cards.
1. No-code integrations: Payment Button and Smartlinks#
If you use Payment Button (Webcheckout) or Smartlinks, the technical integration is already resolved. However, it is necessary to manually activate this option in your Kushki console.When creating or editing your Smartlink or Payment Button in the Console, make sure to enable the toggle corresponding to Apple Pay in the "Payment Methods" section.
No. For No-Code Integrations (Smartlinks, Payment Button) and Custom Integrations (libraries and Kajita), you do not need an Apple Developer account.By using Kushki as your processor, we manage the complexity of certificates with Apple. You only need to host the file we provide to prove that you are the owner of the domain.
If you use Kushki.js (v1 or v2 - hosted fields) or Kajita, it is necessary to perform a domain verification to ensure that your website is authorized to process payments with Apple Pay.Prerequisites: Before starting, make sure you have access to the Kushki Console, specifically the Configuration module.
Once Kushki delivers the file to you, you must host it on your web server. Apple requires this file to be publicly accessible via the HTTPS protocol at a specific path.Create a folder named .well-known in the root of your domain and place the downloaded file there. The final URL should look like this:https://your-domain.com/.well-known/apple-developer-merchantid-domain-associationYou can verify that the file is correctly hosted by running the following command in your terminal or simply pasting the URL into your browser:
You should receive a 200 OK response and the file should be downloadable or visible.
Step 3: Domain registration in the Kushki Console#
With the file correctly hosted, the final step is to register your domain on our platform to complete the association.
Log in to the Kushki Console.
Go to Configuration > Integrations.
Look for the Apple Pay section.
Enter your domain URL (example: your-domain.com) in the corresponding field.
Click on Register or Verify.
At this point, Kushki will communicate with Apple to verify that the file exists on your server. If everything is correct, the domain will be verified.
Return to the Apple console (Merchant IDs section), select your ID, and click Create Certificate under the title Apple Pay Merchant Identity Certificate.
Upload the generated merchant_id.csr file and click Continue.
Download the certificate (merchant_id.cer).
Phase 3: Generate the Apple Pay Payment Processing Certificate#
Once the Merchant ID and the Merchant Identity Certificate have been generated, it is necessary to obtain a Certificate Signing Request.Follow these steps to obtain the certificate:
1.
Create the EC private key (P-256): Run the following command to generate the processing key:
Once you have your certificates and the verified domain, you must proceed with programming the payment button on your website.
Important
To implement the button and for more information, rely on the official Apple Pay on the Web guide.
Follow these steps:
Create the Apple Pay Session: Use your Merchant Identity Certificate (generated in Phase 2) to communicate with Apple's servers. This is mandatory to validate your identity and allow the payment sheet (Wallet) to display on the customer's device.
Decrypt the data: Once the customer authorizes the purchase, Apple will return an encrypted payment object. You must use the private key from your Payment Processing Certificate (generated in Phase 3) to decrypt this package and obtain the card data (DPAN, cryptogram, etc.).
Tokenize with Kushki: Finally, with the card information already decrypted, you must send it to Kushki to generate a secure transport token.
You must consume the endpoint to create a Network Token. Learn how it works in Network Tokens.
Are there special decline codes for Apple Pay transactions? No, because the transaction is processed through the same card network flow, and the existing decline codes apply.
Are there maximum or minimum transaction amounts? No, there are no specific amount limits imposed by Apple Pay.
Does it work within mobile applications? No. Currently, this functionality is only available for purchases using web browsers.
Must domain registration be performed in both UAT (testing) and Production? Yes, Apple requires the domain to be validated in both environments to process payments correctly.
Does 3DS authentication apply to transactions made with Apple Pay? Apple Pay transactions do not require 3DS because the Issuer authorizes the process when the card is registered in the wallet.
Apple Pay Sandox Testing
Test your cards in the Sandbox environment using Apple Pay
