Card Reissue and Transaction Authorization
Cards gain a reissue endpoint and product-based v3 ordering, and corporate integrations get the v3 card
surface. Payouts can now require a wallet signature from the user. Corporate USD accounts receive FedNow deposits. The PCI Compliant SDK is now the recommended path for every card-data surface. Activity status rules are tightened.
What's included
Retail
-
Card reissue —
POST /api/v3/cards/{cardId}/reissuereplaces a card with a new one of the same
format, rail, wallet and chain.- Reasons:
Expiration,Damaged,LostOrStolen,UpdateProduct. - Allowed on
NotActivated,Activeand user-Blockedcards once the card is old enough. - Cards list a new
Reissueentry inallowed_actions.
In active testing: the endpoint will be updated before it is final.
- Reasons:
-
v3 product selection — v3 orders accept
productandproduct_type. On the Visa rail you send all
five ofproduct,product_type,payment_system,designandcard_program, or none of them; none means the issuer's defaults.GET /api/v3/cards/configreturnsproducts[]. v3 card reads addproduct,product_typeandregion. -
v3 fee rule — a v3 order needs
delivery_idonly when that order is priced above zero for the user. -
name_on_cardon v3 — applied and printed in upper case. v1 and v2 still emboss the verified name. -
Restricted top-up token —
POST /api/v1/cards/topup/tokenexchanges a user token that only the top-up estimate and execute endpoints accept. -
Transaction authorization — when your company's
transactionAuthorizationModeisSignature,
every payout must carrytransaction_authorization, a wallet signature over a fixed sentence:POST /api/v1/bank/transfer;POST /api/v3/bank/initiate/{corridor};POST /api/v1/cards/transfer.
POST /api/v2/recipientsaccepts it optionally. -
KYC questionnaire —
POST /api/v2/user/questionary. -
Profile fields —
GET /api/v2/useradds:profile.registration_date;last_login_ipandtags.
-
Configuration —
GET /api/v1/configresolves a company fromX-Company-Id, and returnssdkAllowedDomains,transactionAuthorizationModeand the wallet top-up provider blocks. -
Activity search v3 — up to five repeated
predicateparameters, all of which must match. -
Precise amounts — bank and corridor estimates, the card transfer estimate and the top-up estimate return
*_preciseamounts and rates, and accept amounts as decimal strings where noted.
Corporate
- Card issuance v3 —
POST /api/v3/cards/virtualandPOST /api/v3/cards/plasticacceptdesign,card_programandpayment_system, and requireCardSuorCardCreate.
GET /api/v3/cards/configreturns the corporation's order configuration.GET /api/v3/cardsandGET /api/v3/cards/{cardId}read cards across chains. - Card fields —
card_data.design,card_data.card_programandcard_data.regionon every card read. - Exact amounts —
*_precisewithdecimalson wallets, FX estimates, card fees, delivery methods,
activity amounts and statements. - Permissions —
POST /api/v1/wallets/globalcan be granted throughAccountSu,AccountCreateorAccountManage. - FedNow deposits — activating
AchaddsFedNowdetails to the USD account for receiving FedNow credits. FedNow is for deposits only. - Compression — responses are compressed when the request sends
Accept-Encoding.
Changed behavior
- Activity status (retail API) —
Cancelledno longer appears; cancelled movements readFailed.- A card purchase refunded or reversed in full reads
Failed; a partial refund staysCompleted. - A card purchase stays
Pendinguntil its debit settles. - Card fees are reported in
fee_amountinstead of being folded intorate, and card transactions
carryrrn.
- A card purchase refunded or reversed in full reads
- Card transfer estimate — the fee is reported per token. Top-level
fee_amountis deprecated and
always0. - Corridor quotes — SEPA and Faster Payments quotes include a fee in the debited amount.
Requirements
-
In
Signaturemode, a payout withouttransaction_authorizationis refused with401. Read the mode fromGET /api/v1/configbefore the first payout. -
Card reissue requires the card to be old enough:
- 6 months in production;
- 6 minutes in sandbox.
A reissue of a priced physical card takes the fee through the v2 fee invoice.

