Cards FAQ

Use this guide to answer common questions about how QASH cards behave in production.

Card states

QASH cards support three operational states.

State	Description	Reversible
`active`	Card is fully operational	—
`locked`	Card is temporarily frozen. No transactions are authorized	Yes
`canceled`	Card is permanently closed	No

You can switch between active and locked as many times as needed. Cancellation is permanent and cannot be reversed.

Card transaction payloads include the following fields.

Field	Description
`amount`	Charged amount
`currency`	Transaction currency
`localAmount`	Amount in local currency, when applicable
`localCurrency`	Local currency code
`merchantName`	Merchant name
`merchantCategory`	Merchant category
`merchantCategoryCode`	Merchant category code, also known as MCC
`status`	`pending`, `completed`, `reversed`, or `declined`
`declinedReason`	Reason for decline, when applicable
`authorizedAt`	Authorization timestamp in ISO 8601 format
`postedAt`	Settlement timestamp in ISO 8601 format
`cardType`	`virtual` or `physical`

The card draws from the user’s QASH USDC balance — there is no separate card-funding step or card-specific wallet to manage.

Fund the user’s QASH balance with Deposit funds. Once the deposit is confirmed, the balance is available for card spending.

Withdraw funds from the user’s QASH balance to a bank account with Payout, through a supported provider such as irisbank, cobre, or borderless.

Card balances are backed by tokens held in smart contracts on Polygon and reconciled in real time with the QASH ledger.