Choose the payment flow first
Virtual Terminal and hosted requests
Apple Pay and Google Pay are available for supported Virtual Terminal payment links, invoices, and recurring payment flows after activation. Confirm the customer experience and eligible devices for the flow your business will use.
Check each software connection separately
A gateway can support a wallet without every store plugin, invoice connector, or physical terminal supporting it. Check the exact checkout and release. An Apple Pay logo on one product page is not proof of compatibility with your whole setup.
Apple Pay on your website
Two documented setup paths
The Apple Pay web guide distinguishes setups managed by Blackstone and setups managed by the merchant. Both require account enablement and HTTPS domains. When Blackstone manages the setup, it provides the relevant configuration. When you manage it, you use your own Apple identity and certificates. Domain verification and payment processing must both be configured.
Decide who maintains it
Before implementation, agree on who manages domain verification, certificates if applicable, testing, and future changes. Keep private keys and gateway credentials off public pages and out of routine support messages.
Google Pay on your website
Domain approval and payment handling
The Google Pay web guide requires approved production domains, HTTPS, provider credentials, and a Google Pay checkout that passes the returned payment token to a server. The application must calculate the final amount and display the payment result.
What your customer sees
Confirm that the displayed amount includes the intended products, tax, delivery, and any permitted price adjustments. If a customer cannot use the wallet, provide another supported payment method rather than leaving checkout blocked.
Test before advertising acceptance
Follow a payment through to the records
Use the approved test environment to check success, decline, cancellation, and a retry. Verify the order or invoice status and the reference used for reconciliation. Include refunds and repeat billing only if the proposed integration supports those workflows.
Separate online from in person
Contactless acceptance at a terminal and a wallet button in an online checkout have different setup paths. Confirm the actual terminal model or mobile device, account activation, and software before promising acceptance.