Apple Pay

Apple Pay lets your shoppers pay with the cards stored in their Apple Wallet, using Face ID, Touch ID, or a passcode to authorise. Enabling Apple Pay with Plexy is a one-time setup in your dashboard at Settings → Integrations, plus per-platform steps below.

Web setup

For Apple Pay on the web you only need to validate the domain you serve checkout from. Plexy holds the merchant identity certificate, so no certificate upload happens on the web side.

Hosted Checkout

If you use Plexy Hosted Checkout through Payment Links, Apple Pay works out of the box. The domain verification steps below are required only when Apple Pay is displayed directly on your website through the Plexy Web SDK.

Before you start

Requirement	Description
Plexy account	You need access to Plexy Dashboard.
Website domain	Example: `shop.example.com`.
Plexy Web SDK integration	Payment components must be integrated on your website.
Integration manager contact	Your Plexy technical integration manager must receive your domain list.

Prepare the domain list

List every domain where Plexy Web SDK payment components can be displayed, for example shop.example.com, checkout.example.com, and example.com.

Send domains to Plexy

Send the full domain list to your Plexy technical integration manager. Plexy must register the merchant domains before you complete domain verification in the dashboard.

Download the domain association file

After Plexy confirms the domains are registered, open Web Integration → Apple Pay Domain Verification in the Plexy dashboard and click Download verification file. This downloads apple-developer-merchantid-domain-association (no file extension).

Host the file on your domain

Serve the file at:

https://<your-domain>/.well-known/apple-developer-merchantid-domain-association

The file must be reachable over HTTPS, without redirects, and without an added extension.

Check file availability

Open the file URL in a browser and confirm HTTP status 200. The file must not be blocked by firewall, CDN, WAF, or authentication, and your server must not modify its content.

Verify and register the domain

Back in the Plexy dashboard, type the same domain into the Domain verification input and click Verify. On success, click Register. The domain now appears under Registered domains.

Configure the Web SDK merchant name

Configure Apple Pay in your Web SDK payment-method configuration with the merchant name from Plexy Dashboard Settings → Merchant Settings → merchantName.

Warning

Each domain that serves your Apple Pay checkout must be registered. Subdomains
count separately — register www.example.com and checkout.example.com if
both serve checkout.

Do not skip Plexy registration

Domain verification in the Plexy dashboard should be done only after Plexy confirms that the domain has been registered on its side. If Apple Pay is shown on a domain that was not registered and verified, Apple Pay may not appear or may fail during payment.

Once the domain is registered, the Plexy Web SDK renders the Apple Pay button automatically.

After domain verification and Web SDK configuration, check that:

the Apple Pay button is displayed on the verified domain;

the Apple Pay sheet opens;

the merchant name is displayed correctly;

the payment token is created successfully;

the payment is processed by Plexy.

Availability

Apple Pay is available only in supported browsers, devices, regions, and cards.

Web SDK

Mount Drop-in or individual components to render Apple Pay on the web.

Native setup (iOS)

Prerequisites

An Apple Developer Program membership.

Access to the Plexy dashboard's Settings → Integrations page (requires a store).

For native iOS apps you'll generate a Certificate Signing Request (CSR) in the Plexy dashboard, sign it with Apple, then upload the resulting .cer back to Plexy. This binds your Apple Merchant ID to Plexy so the SDK can decrypt payment tokens.

CSR ownership

Do not generate your own private key or CSR for this integration. Plexy generates and stores the private key because Plexy decrypts Apple Pay payment tokens.

Key concepts

Term	Meaning
CSR	Certificate Signing Request generated by Plexy and uploaded by the merchant to Apple.
Private key	Secret key generated and stored by Plexy. It is not shared with the merchant.
Payment Processing Certificate	Certificate issued by Apple for the merchant's Apple Merchant ID.
Apple Merchant ID	Apple identifier used by the merchant app to accept Apple Pay payments.

Info

The CSR does not contain the private key. It contains the public key and certificate request data. Apple uses the Payment Processing Certificate to encrypt Apple Pay payment data; Plexy uses the corresponding private key to decrypt the payment token.

Create a Merchant ID in Apple Developer

In Apple Developer →
Identifiers,
create a new Merchant ID (for example, merchant.com.yourbrand.app).

Generate a CSR in the Plexy dashboard

In Settings → Integrations → Apple Pay certificates, enter a label, then
click Generate CSR. The dashboard downloads a .csr file and adds a new
certificate row in pending status.

Create the Payment Processing Certificate in Apple Developer

On your Merchant ID's page in Apple Developer, click Create Certificate
under Apple Pay Payment Processing Certificate, upload the .csr, then
download the signed .cer Apple returns.

Upload the signed certificate to Plexy

Back in the Plexy dashboard, on the pending certificate row, click Upload
certificate and select the .cer. The row moves to active once Plexy
verifies it. Plexy validates that the certificate matches the private key generated by Plexy, is a Payment Processing Certificate, is valid and not expired, and belongs to the expected Apple Merchant ID.

Enable Apple Pay in Xcode

In Xcode, open your target's Signing & Capabilities, add the Apple
Pay capability, and select the same Merchant ID. The Plexy iOS SDK reads
the Merchant ID from your app and uses the certificate Plexy now holds to
decrypt payment tokens.

What to upload

File	Upload to Apple?	Upload to Plexy?
`.csr` from Plexy	Yes	No
`.cer` from Apple	No	Yes
Private key	No	No
`.p12` / `.pfx`	No	No
Merchant Identity Certificate	No	No

Wrong file types

For this setup, upload only the Apple-issued .cer Payment Processing Certificate to Plexy. Do not upload Apple Merchant Identity Certificates, Apple Development or Distribution Certificates, APNs Certificates, TLS/SSL certificates, private keys, .p12, or .pfx files.

Your iOS app must use the same Merchant ID that was used to create the Payment Processing Certificate:

Info

Apple Pay is not available on Android. For Android, see Google
Pay.

iOS SDK

Render Apple Pay in your iOS app with Drop-in or Components.

React Native SDK

Apple Pay on iOS via the Plexy React Native wrapper.

Flutter SDK

Apple Pay on iOS via the Plexy Flutter wrapper.

Troubleshooting

Warning

Domain verification fails with 404. The file must be served at the exact
.well-known/apple-developer-merchantid-domain-association path, over HTTPS,
without a redirect and without an added extension.

Warning

Certificate stuck in pending. The uploaded .cer must be signed against
the CSR Plexy generated. If the row never moves to active, generate a fresh
CSR in Plexy and re-issue the certificate in Apple Developer.

Warning

iOS app does not present the Apple Pay sheet. Confirm the Apple Pay
capability is enabled in Xcode and the selected Merchant ID matches the one
tied to your active certificate in Plexy.

Error	Cause	How to fix
Plexy cannot validate certificate	Wrong certificate uploaded	Upload the Payment Processing Certificate issued from the Plexy-generated CSR
Plexy cannot decrypt token	CSR was not generated by Plexy	Generate a new CSR in Plexy and create a new certificate in Apple
Apple Pay token rejected	Token was modified	Send the original token without changes
Merchant ID mismatch	App uses another Merchant ID	Use the same Merchant ID in Apple Developer Portal, the iOS app, and Plexy Dashboard
Wrong certificate type	Merchant Identity Certificate uploaded	Upload the Payment Processing Certificate
Apple Pay fails in Web SDK	Domain was not registered by Plexy	Send the domain to your Plexy integration manager
Merchant name is missing	`merchantName` is not configured	Add `merchantName` to the Web SDK payment component config
Wrong merchant name is displayed	Incorrect `merchantName` value	Update `merchantName` in the Web SDK config

Web setup#

Before you start#

Native setup (iOS)#

Prerequisites#

Key concepts#

What to upload#

Troubleshooting#

Web setup

Before you start

Native setup (iOS)

Prerequisites

Key concepts

What to upload

Troubleshooting