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
  • Status Transition Rules
  • Request Parameters
  • Response Parameters
  • Example Request Body
  • Example Response Body
  1. Payment methods H2H
  2. TOKEN

Update Token Status

{{url}}/ecom/execute_request/token/v1/state/update

Status Transition Rules

  • ACTIVE → SUSPENDED – An active token can be suspended (e.g., for temporary blocking).

  • SUSPENDED → ACTIVE – A suspended token can be reactivated (e.g., after unblocking).

  • ACTIVE → DELETED – An active token can be deleted permanently.

  • SUSPENDED → DELETED – A suspended token can be deleted if the user does not restore activity.

  • DELETED → any other status – Not possible.

Request Parameters

Parameter
Description
Data Format
Required
Example

token

Token ID

string

Yes

SRrSBe5DOb7lrZ_FS46fihty

state

New token status

string

Yes

SUSPENDED

Response Parameters

Parameter
Description
Data Format
Example

tokenUpdated

Indicates whether the token status was updated

boolean

true / false

customerId

Customer ID

string(255)

12345

token

Token ID

string

SRrSBe5DOb7lrZ_FS46fihty

Example Request Body

jsonКопіюватиРедагувати{
    "token": "-s9UCfCNN0YMk4ZOyZX8pWAt",
    "state": "SUSPENDED"
}

Example Response Body

jsonКопіюватиРедагувати{
    "tokenUpdated": true,
    "customerId": "senderCustomerId",
    "token": "-s9UCfCNN0YMk4ZOyZX8pWAt"
}
PreviousRetrieve Token DataNextToken Statuses

Last updated 2 months ago