Statuses & Enums

Every integer enum in the API is documented on this page, organized by resource. Where the same field name carries a different value set in different contexts (as with transStatus), each context is listed separately with an explicit warning.

Cardholder status

Field: CardholderListItem.status, CardholderView.status

Value	Name	Meaning
`0`	Pending	Transitional state — observed briefly during status transitions, not a stable resting state
`1`	Approved	KYC passed — Cards can be issued
`2`	Compliance Decline	KYC failed by the compliance provider
`3`	Under Review	Submitted for compliance review; awaiting outcome
`4`	Draft	Created but not yet submitted for compliance review
`5`	Deleted	Cardholder removed via `DELETE /cardholders/{cardholderId}`
`6`	Error	Processing error during compliance review
`7`	Admin Decline	Manually declined by platform administration

See Cardholders & the Compliance Lifecycle.

Card approval status

Field: CardViewMasked.cardStatus

This is the issuance approval status — whether the card creation request was approved by the platform. Different from issuerCardStatus (operational lifecycle).

Value	Name	Meaning
`0`	Pending	Card issuance request awaiting approval
`1`	Approved	Card issuance approved
`2`	Declined	Card issuance declined

Card operational status (issuer card status)

Field: CardViewMasked.issuerCardStatus, CardListItem.status, GET /cards/{cardId}/status

This is the card's operational lifecycle status after issuance is approved.

Value	Name	Meaning
`0`	Pending	Transitional state
`1`	Active	Card is operational and can be used for transactions
`2`	On Hold	Card temporarily blocked and all authorization attempts declined
`3`	Closed	Card permanently closed — terminal state
`4`	Not Activated	Physical card issued but not yet activated by the Cardholder

Legal transitions via PUT /cards/{cardId}/status: Active ↔ On Hold only (1 ↔ 2).

🚧
CardListItem.status in the list endpoint uses the same 0–4 values as issuerCardStatus. The separate cardStatus field (0–2) is only returned by GET /cards/{cardId} (the single-card detail endpoint). The list endpoint returns only the operational status.

See Cards: Virtual & Physical.

Transaction status

Field: TransactionsViewResponse.transStatus, FeesViewResponse.transStatus

Used on card transactions and card fees retrieved via GET /cards/transactions and GET /cards/fees.

Value	Name	Lifecycle phase
`1`	Pending	Authorization hold placed — not yet cleared
`2`	Cleared	Transaction posted after merchant batch processing
`3`	Completion	Settlement complete
`4`	Declined	Authorization declined — no hold placed
`5`	Error	Processing error

Transaction type

Field: TransactionsViewResponse.transType, GET /cards/transactions filter parameter transType

Code	Name
`1`	`authorization`
`2`	`authorization_advice`
`3`	`authorization_clearing`
`4`	`authorization_clearing_chargeback`
`5`	`authorization_clearing_chargeback_completed`
`6`	`authorization_clearing_chargeback_provisional_credit`
`7`	`authorization_clearing_chargeback_provisional_debit`
`8`	`authorization_clearing_chargeback_reversal`
`9`	`authorization_clearing_chargeback_writeoff`
`10`	`authorization_clearing_representment`
`11`	`authorization_incremental`
`12`	`authorization_reversal`
`13`	`authorization_reversal_issuerexpiration`
`14`	`authorization_standin`
`15`	`fee_charge`
`16`	`fee_charge_pending`
`17`	`fee_charge_reversal`
`18`	`gpa_credit`
`19`	`gpa_credit_authorization`
`20`	`gpa_credit_authorization_reversal`
`21`	`gpa_credit_issueroperator`
`22`	`gpa_credit_networkload`
`23`	`gpa_credit_networkload_reversal`
`24`	`gpa_credit_pending`
`25`	`gpa_credit_pending_reversal`
`26`	`gpa_credit_reversal`
`27`	`gpa_debit`
`28`	`gpa_debit_issueroperator`
`29`	`gpa_debit_reversal`
`30`	`msa_credit`
`31`	`msa_credit_pending`
`32`	`msa_credit_pending_reversal`
`33`	`msa_credit_reversal`
`34`	`msa_debit`
`35`	`pindebit`
`36`	`pindebit_atm_withdrawal`
`37`	`pindebit_authorization`
`38`	`pindebit_authorization_clearing`
`39`	`pindebit_authorization_reversal_issuerexpiration`
`40`	`pindebit_balanceinquiry`
`41`	`pindebit_cashback`
`42`	`pindebit_chargeback`
`43`	`pindebit_chargeback_completed`
`44`	`pindebit_chargeback_provisional_credit`
`45`	`pindebit_chargeback_provisional_debit`
`46`	`pindebit_chargeback_reversal`
`47`	`pindebit_chargeback_writeoff`
`48`	`pindebit_refund`
`49`	`pindebit_refund_reversal`
`50`	`pindebit_reversal`
`51`	`pindebit_transfer`
`52`	`programreserve_credit`
`53`	`programreserve_debit`
`54`	`refund`
`55`	`token_activation_request`
`56`	`token_advice`
`57`	`transaction_unknown`
`58`	`transfer_peer`
`59`	`transfer_program`
`60`	`activate_account`
`61`	`adjustment_advice`
`62`	`balance_adjustment`
`63`	`balance_reversal`
`64`	`clear_negative_balance`
`65`	`close_account`
`66`	`create_account`
`67`	`create_purse`
`68`	`credit_adjustment`
`69`	`embossing_pending`
`70`	`foreign_exchange_fee`
`71`	`mark_fraudulent`
`72`	`memo`
`73`	`overwrite_card_status`
`74`	`pin_change`
`75`	`pin_query`
`76`	`refund_advice`
`77`	`authorization_declined`
`78`	`remove_fraud`
`79`	`authorization_reversal_advice`
`80`	`card_load`
`81`	`pindebit_cashwithdrawal`
`82`	`pindebit_preauth`
`83`	`authorizationexpiry`
`84`	`returnreversal`
`85`	`balanceinquiry`
`86`	`cashout`
`87`	`refund_authorization`
`88`	`card_unload`
`89`	`authorization_reversal_settled`
`99`	`other`

Transfer status

Field: TransferResponse.transStatus (from POST /wallets/transfer)

❗️
This is a completely different enum from Transaction status above, despite the identical field name. Never mix these two up: a transStatus of 1 means Pending on a transaction but Approved on a transfer.

Value	Name	Meaning
`0`	Pending	Transfer submitted, processing
`1`	Approved	Transfer completed successfully
`2`	Declined	Transfer rejected (e.g. insufficient balance)
`3`	Partial	Transfer completed for less than the requested amount
`4`	Error	Processing error

See Transfer Internal Fiat Funds.

Card design status

Field: Account Management card design slot status

Value	Name	Meaning
`0`	Pending	Design submitted, awaiting review
`1`	Approved	Design approved, cards can be issued using this `cardType` slot
`2`	Rejected	Design rejected, resubmission required

See Card Programs & Designs.

Gender

Field: CardholderCreate.gender, CardholderUpdate.gender, CardholderView.contact.gender

Value	Name
`0`	Male
`1`	Female
`2`	Other

Currency

Field: CardBalance.currency, WalletView.walletCurrencyId

Derived from the Program — set at Program creation and cannot be changed.

Value	Currency	ISO 4217 code
`0`	US Dollar	USD
`1`	Canadian Dollar	CAD
`2`	British Pound Sterling	GBP
`3`	Euro	EUR

See ISO Code Conventions and Accounts, Wallets & Deposit Addresses.

SumSub enabled

Field: CardholderCreate.sumsubEnabled, CardholderView.sumsubEnabled

Value	Meaning
`0`	Standard compliance flow (Didit-hosted KYC) — default
`1`	SumSub token-based KYC flow

Wallet transfer destination type

Field: POST /wallets/transfer request body destinationType

Value	Meaning
`0`	Destination is a `walletId`
`1`	Destination is a `cardId`

OTP status

Field: OtpRetrieveResponse.status (from GET /otp/{token})

Value	Meaning
`pending`	Subscription active — no 3DS challenge event has triggered yet
`received`	An OTP has been generated for an active 3-DS challenge — `code` field is populated
`expired`	OTP's `expiresAt` timestamp was reached before it was used
`consumed`	OTP was used successfully to complete a transaction

Support ticket status

Field: Account Management support ticket status

Value	Meaning	Who acts next
`open`	Awaiting support response	Platform
`pending`	Support has responded — awaiting Tenant reply	Tenant
`resolved`	Support marked as resolved	Tenant (can re-open within 72 hours)
`closed`	Resolved without re-opening for 72 hours	Terminal — raise new ticket if needed

Support ticket priority

Field: Account Management support ticket priority

Based on the ITIL Priority Matrix (Urgency × Impact):

Value	Level	Typical use
`1`	Critical	Platform-wide service disruption; suspected data breach
`2`	High	production Program fully down; multiple Cardholders affected
`3`	Medium	Significant feature degraded; compliance processing blocked
`4`	Low	Single Cardholder issue; minor discrepancy
`5`	Informational	General query; non-urgent follow-up — default if not set

See Support Tickets.