Skip to main content

Transaction Lifecycle

This guide provides an overview of how card transactions work in the Issuing API, including the transaction flow, lifecycle states, and transaction types.

Overview

Card transactions are created automatically when cardholders use their cards for purchases, ATM withdrawals, or other card-based transactions. As an issuer, you can monitor these transactions, view their status, and perform operations like refunds.

Transaction Lifecycle

Card transactions follow a standard authorization-capture flow with support for reversals and refunds:

Transaction Flow

The following sequence diagram shows how a card transaction flows through the system:

Transaction Statuses Overview

Card transactions can be in one of four states:
StatusDescriptionNext Actions
pendingTransaction authorized but not capturedCan be captured or voided
postedTransaction captured and finalizedCan be refunded
declinedAuthorization failedNo further action
voidAuthorization reversedNo further action
For detailed information about each status, see Transaction Statuses.

Transaction Types

Card transactions can have different intents:
IntentDescriptionExample
chargeCard purchase or paymentCardholder buys goods at merchant
refundRefund of a previous chargeMerchant refunds a purchase
topupAdding funds to card accountCardholder adds money to prepaid card
withdrawATM withdrawalCardholder withdraws cash
feeService feeMonthly card fee, ATM fee
cashbackCashback rewardRewards program cashback
interestInterest paymentInterest earned on balance

Key Concepts

Authorization vs Capture

  • Authorization: Holds funds but doesn’t transfer them. Transaction status is pending.
  • Capture: Transfers funds and finalizes the transaction. Transaction status becomes posted.

Reversal vs Refund

  • Reversal (Void): Cancels a pending authorization before capture. Funds are released immediately.
  • Refund: Returns funds from a posted transaction. Creates a new refund transaction.

Next Steps