Skip to content

Last Updated: 15 July 2025 | Change Log

Apple Pay

Make an Apple Pay payment by providing the encrypted payload (wallet token) in the payments request.

Apple Pay is not yet supported when setting up a recurring payment.

1. Basic Request

application/json

Provide the encrypted Apple Pay payload

{ "transactionReference": "Memory265-13/08/1876", "merchant": { "entity": "default" }, "instruction": { "method": "applepay", "paymentInstrument": { "type": "encrypted", "walletToken": "{\"version\": \"EC_v1\",\"data\": \"kdHd..GQ==\",\"signature\": \"MIAGCSqGSIb3DQEH...AAA\",\"header\": {\"transactionId\": \"d3b28af..f8\",\"ephemeralPublicKey\": \"MFkwE..Q==\",\"publicKeyHash\": \"dxCK..6o=\"}}" }, "narrative": { "line1": "trading name" }, "value": { "currency": "GBP", "amount": 42 } } }

2. Add additional features

Note: 3DS (for Googlepay) and FraudSight are not yet available for wallets

3. Response

Features that change the API flow

Certain features add additional requests and responses:

  • Auto Settlement - automatic 202 - sentForSettlement following authorization.
    • If any of the AVS/CVC response riskFactors are marked as notMatched the payment will be sentForCancellation automatically by default but can be disabled.
application/json
No response example