AlliancePay
🇬🇧 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

Using an authorization token

PreviousAuthorizationNextKey Management Overview

Last updated 2 months ago

After decrypting the JWE response (see: ) for the authorization request "/api-gateway/authorize_virtual_device", the session token and its expiration parameters are obtained:

  • "tokenExpirationDateTime": "2025-02-27 12:12:34.0430 +0000" // UTC+00:00

  • "tokenExpiration": "2025-02-27 14:12:34.430+02:00" // UTC+02:00 Kyiv

Potential Issues

  1. Expired Authorization Token Due to Inactivity

  • If there is no activity for serviceCode for more than 200 days, API access is automatically revoked.

  • When attempting to execute an authorization request to "/api-gateway/authorize_virtual_device", the following error occurs: "b_auth_token_expired"

Resolution:

  • To resolve this issue, contact the support team.

  • After the issue is resolved, new parameters will be provided in the authorization response, which must be updated before making further API requests.

  1. Expired Current Token

  • If the following error occurs: "b_expired_token"

  • A new authorization request to "/api-gateway/authorize_virtual_device" must be made.

Decryption Example