Digital Wallet Integration

Card-not-present Apple Pay / Google Pay and card-present NFC are distinct integration paths. A supported SDK method does not grant processor activation, network certification, or permission to use a wallet in production.

Web and in-app wallets

Use GatewayPayClient.wallet in TypeScript or Kotlin. The consumer methods are validateApplePaySession, chargeApplePay, authorizeApplePay, getGooglePayConfig, chargeGooglePay, and authorizeGooglePay. Use the request types and API reference for the current request contract, not a vendor-wire example.

Apple Pay on the web first requires merchant validation from the Apple-provided validation URL. Complete that validation with the returned merchant session, then submit the encrypted payment token through the supported payment flow. Never decrypt a wallet token in a merchant application or log it.

Apple Pay registration belongs to the organization. Locations resolve that completed registration; availability also requires an active compatible route and organization enablement. Missing or incomplete registration fails closed. Do not treat wallet availability as a per-location checkbox or substitute another organization's merchant identity.

For Google Pay, obtain the configured gateway and merchant parameters rather than guessing the gateway identifier. Use PAYMENT_GATEWAY tokenization; DIRECT decryption is unsupported. Production review and account/route configuration are prerequisites. Google Wallet passes are not Google Pay payment acceptance.

For hosted checkout, use the session's enabled methods and device/browser availability. Real Apple-capable hardware, a test wallet, trusted HTTPS, and cardholder interaction are required to exercise an Apple Pay flow. A browser redirect or wallet-sheet dismissal is not settlement or payment success: inspect the authoritative terminal outcome.

Certificates and scope

Apple's merchant identity certificate authenticates merchant-session validation; the payment-processing certificate protects payment tokens. They are different assets and registrations. Use the approved processor-decryption setup and keep private keys out of apps, logs, and tickets. Encrypted transport does not by itself establish a PCI scope determination or compliance attestation.

Apple Tap to Pay on iPhone has separate onboarding, terminal, key, and network approvals. It is not enabled by CNP Apple Pay registration.

Card-present wallets

Certified terminals handle NFC/contactless wallet interaction. Use the approved Android runtime or Bolt terminal flow, not CNP wallet endpoints or hand-assembled EMV fields. Keep unknown results unresolved for reconciliation rather than automatically retrying.

See Apple Pay environment setup and Google Pay Web API for browser prerequisites.