AlliancePay
🇬🇧 English
🇺🇦 Українська🇬🇧 English
🇬🇧 English
🇺🇦 Українська🇬🇧 English
  • E Commerce platform AlliancePay v2.32.0
  • Authentication
  • Data Encryption
  • Authorization
  • Using an authorization token
  • Key Management Overview
    • PURCHASE Collection Example
    • A2C Collection Example
  • Payment methods H2H
    • PURCHASE
      • PURCHASE Request - Step 1
      • PURCHASE Request - Step 2
    • A2C
    • C2A
      • C2A Transaction Request - Step 1
      • C2A Transaction Request - Step 2
    • ApplePay decrypted
      • PURCHASE
        • Payment Processing Request - Step 1
        • Payment Processing Request - Step 2 (3DS)
      • C2A
        • C2A request Step 1
        • C2A request Step 2 (3DS)
    • ApplePay encrypted
      • Request aPay support on the page
      • Request to receive aPay merchant data
      • Merchant validation request
      • Session Establishment Request in aPay
      • Payment Processing Request
    • GooglePay™ decrypted
      • PURCHASE
        • Payment Processing Request - Step 1
        • Payment Processing Request - Step 2 (3DS)
      • C2A
        • C2A request Step 1
        • C2A request Step 2 (3DS)
    • GooglePay™ encrypted
      • Google Pay™ Documentation
      • Google Pay™ Support Request on the Page
      • Google Pay™ Merchant Data Retrieval Request
      • Payment request
    • REFUND
    • TOKEN
      • PURCHASE
        • Token payment request Step 1
        • 3DS token payment request Step 2
      • C2A
        • Token payment request Step 1
        • 3DS token payment request Step 2
      • Token Creation
      • Retrieve Token by CustomerId
      • Retrieve Token Data
      • Update Token Status
      • Token Statuses
    • Account Verification
      • Card Verification Request Step 1
      • Card verification request Step 2
    • Getting data
      • By OPERATION_ID
      • By merchantRequestId
    • Getting a balance
    • Callback
  • Payment methods HPP
    • PURCHASE
      • Creating an order
      • Receiving order data
    • REFUND
    • Callback
    • Order statuses
  • Dictionary
    • Transaction status
    • Test cases
    • Error codes
    • Value actionCode, responseCode
    • Limits
    • Instructions for reconciliation by registers
      • Fields Description in Registers
    • Whitelist IP addresses and URLs
  • History of changes
Powered by GitBook
On this page
  1. Payment methods H2H

ApplePay encrypted

PreviousC2A request Step 2 (3DS)NextRequest aPay support on the page

Last updated 2 months ago

  1. The client clicks the "Pay for Order" button on the website or application.

  2. The WebPage executes the Apple Pay Support Request script to check whether Apple Pay is supported on the current page.

  3. If the client’s device does not support Apple Pay, the client will not be able to use this payment method, and the request will be rejected.

  4. If Apple Pay is supported, the WebPage sends an optional Merchant Data Request to Apple Pay. Merchant-side hard-coded Apple Pay data can be used.

  5. The WebPage executes the Merchant Validation script via Apple Pay to confirm the merchant data.

  6. Apple Pay returns a callback containing the validationUrl parameter.

  7. The client clicks the Pay with Apple Pay button to confirm the selection of this payment method.

  8. A session with Apple Pay is established, and the client’s device is ready to interact with Apple Pay.

  9. In response to session establishment, Apple transmits tokenized card data.

  10. The client is presented with a list of available cards stored on the device for payment.

  11. The client selects a card for payment.

  12. The client’s device script interacts with Apple’s server to obtain the encrypted paymentToken.

  13. Client authentication is performed via biometrics or password.

  14. Apple generates the paymentToken and transmits it to the WebPage for further processing.

  15. The WebPage sends a Payment Processing Request using the received token.

  16. If 3D Secure (3DS) verification is required, the 3DS process is initiated. If 3DS is not required, the transaction proceeds without it.

  17. Non-3DS Flow:

  • The payment is authorized.

  • A response to the Payment Processing Request is generated.

  1. 3DS Flow:

  • Additional verification is performed via 3DS.

  • Upon verification completion, a response to the Payment Processing Request is returned, including the redirect3dsUrl parameter.

  • The WebPage redirects the client to the redirect3dsUrl page for 3DS authentication.

  • The client confirms the transaction via 3DS.

  • The transaction is authorized.

  1. A callback is sent to the merchant at the specified notificationUrl, containing transaction details.

  2. The client is redirected to a Result Page, confirming the payment completion.