CardAuthorizationRequest

Sent in real time when a cardholder initiates a transaction. Unlike notification webhooks, this is a synchronous request — Altery waits for your response to decide whether to approve or decline the transaction.

To reduce the total authorization time, Altery performs its own authorization checks in parallel with the partner decision request. The transaction is approved only if both Altery and you approve the authorization. If either Altery or you decline, the authorization will be declined.

Authorization requests are not retried. Each CardAuthorizationRequest is a single real-time decision, and a missing or late response is treated as a decline.

Request Payload Fields

Sample Request Payload

{
  "event":"CardAuthorizationRequest",
	"authorizationId": "fd01ce3c-0799-43be-b4cd-b95dd107d4d8",
  "cardId": "f16ba382-eb42-481a-b08f-c57bdc9aae24",
  "transactionAmount": 800,
  "transactionCurrencyCode": "GBP",
  "accountAmount": 1000,
  "accountCurrencyCode": "EUR",
  "merchantId": "SHP00000000057",
  "merchantName": "aliexpress.com",
  "merchantCategoryCode": "5651",
  "merchantCity": "London",
  "entryModeType": "Irrelevant",
  "isDeclined": true,
  "createdAt": "2019-08-24T14:15:22Z",
  "date": "2019-08-24T14:15:22Z"
}

Response Format

Your endpoint must return HTTP 200 with the following JSON body:

Sample Response — Approved

{
  "authorize": "true",
  "errorCode": 0,
  "errorMsgs": []
}

Sample Response — Declined

{
  "authorize": "false",
  "errorCode": 21,
  "errorMsgs": ["Not sufficient funds"]
}

Decline Behavior

The transaction will be declined in any of the following cases:

Decline Reason Codes

When declining a transaction, set errorCode to the appropriate value from the table below.

Altery uses these exact codes internally when reporting decline reasons to the card scheme. While using them is not mandatory, we strongly recommend aligning with this format to ensure consistent reporting across the full transaction flow.