Skip to content

Get Card Transaction Process ​

GET /openapi/v2/cards/transactions/process

Read stored transaction and fee-processing steps for a card owned by the current tenant. This endpoint does not query the service provider, synchronize status, or initiate recovery.

ItemValue
HTTP methodGET
Request path/openapi/v2/cards/transactions/process
Request typequery

Request parameters ​

FieldTypeRequiredDescription
cardIdstringYesCard ID owned by the current tenant.
transactionIdstringYesitems[].id from List Card Transactions: a service-provider transaction ID for purchases, refunds, or voids; a platform order number for recharges or withdrawals.
transactionTypestringYesThe row's unified type, case-sensitive: CONSUMPTION, REFUND, VOID, RECHARGE, or WITHDRAWAL.

The transaction ID, type, and card must match. Transactions from another tenant or card, or missing transactions, cannot be queried. Do not use a raw provider type such as auth as transactionType.

Request example ​

http
GET /openapi/v2/cards/transactions/process?cardId=card_001&transactionId=TXN_001&transactionType=CONSUMPTION

Response data ​

data is an array of processing steps, without pagination:

FieldTypeDescription
[].stepTypestringStep type; see the table below.
[].stagestring/nullProcessing stage or raw business type of this step; meaning varies by step and values may expand. Not the request's unified transaction type.
[].statusstring/nullStatus of this step, not the final state of the whole purchase or order; see below.
[].providerStatusstring/nullRaw service-provider status retained for diagnostics. Use status for business display and decisions.
[].amountstring/nullDecimal string: absolute amount for transaction and order steps, or the associated fee amount for fee steps.
[].currencystring/nullCurrency of this step's amount.
[].referenceNostring/nullService-provider transaction ID, platform flow number, order number, or fee order number.
[].occurredAtstring/nullPlatform processing time in ISO 8601. Uses processing or completion time, falling back to update or creation time; not the provider's transaction occurrence time.
[].notestring/nullAdditional information; order steps may contain a failure code.

Step types and statuses ​

stepTypeMeaningKnown status values
CONSUMPTION, REFUND, VOIDStored purchase, refund, or void recordSUCCESS, FAILED, VOID, PROCESSING; null for historical records without a stored status
ORDER_FLOWRecharge or withdrawal order flowCREATED, PROCESSING, SUCCESS, FAILED
ORDER_RESULTCurrent order result when no flow records existCREATED, PROCESSING, SUCCESS, FAILED
FEE_CHARGEFee step, using actual charge status when availableNOT_STARTED, PROCESSING, UNKNOWN, SUCCESS, FAILED; historical fallback to fee-order status may also return CREATED or FROZEN

Query semantics ​

  • Only stored records are returned. Missing authorization, posting, or refund steps are not reconstructed; webhook receipt and delivery notifications are excluded.
  • Multiple refunds with explicit links to the original purchase on the same tenant, card, and service provider are included in its process. Missing or ambiguous relationships are not inferred.
  • Sorted by occurredAt ascending, then referenceNo ascending for equal times; missing timestamps are last. These are platform processing records, not a guarantee of the provider event sequence.
  • This is the current state of stored records, not an immutable event snapshot. Do not sum step amounts to calculate purchase principal or actual total debit. See List Card Transactions for whole-transaction status and amount definitions.

Response example ​

A single stored purchase step, for illustration; a complete authorization and posting history is not guaranteed:

json
{
  "code": 200,
  "msg": "Operation successful",
  "data": [
    {
      "stepType": "CONSUMPTION",
      "stage": "auth",
      "status": "SUCCESS",
      "providerStatus": "succeed",
      "amount": "10.5",
      "currency": "USD",
      "referenceNo": "TXN_001",
      "occurredAt": "2026-10-10T02:00:00Z",
      "note": null
    }
  ]
}