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}/reissue replaces a card with a new one of the same
    format, rail, wallet and chain.

    • Reasons: Expiration, Damaged, LostOrStolen, UpdateProduct.
    • Allowed on NotActivated, Active and user-Blocked cards once the card is old enough.
    • Cards list a new Reissue entry in allowed_actions.

    In active testing: the endpoint will be updated before it is final.

  • v3 product selection — v3 orders accept product and product_type. On the Visa rail you send all
    five of product, product_type, payment_system, design and card_program, or none of them; none means the issuer's defaults. GET /api/v3/cards/config returns products[]. v3 card reads add product, product_type and region.

  • v3 fee rule — a v3 order needs delivery_id only when that order is priced above zero for the user.

  • name_on_card on v3 — applied and printed in upper case. v1 and v2 still emboss the verified name.

  • Restricted top-up token — POST /api/v1/cards/topup/token exchanges a user token that only the top-up estimate and execute endpoints accept.

  • Transaction authorization — when your company's transactionAuthorizationMode is Signature,
    every payout must carry transaction_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/recipients accepts it optionally.

  • KYC questionnaire — POST /api/v2/user/questionary.

  • Profile fields — GET /api/v2/user adds:

    • profile.registration_date;
    • last_login_ip and tags.
  • Configuration — GET /api/v1/config resolves a company from X-Company-Id, and returns
    sdkAllowedDomains, transactionAuthorizationMode and the wallet top-up provider blocks.

  • Activity search v3 — up to five repeated predicate parameters, all of which must match.

  • Precise amounts — bank and corridor estimates, the card transfer estimate and the top-up estimate return *_precise amounts and rates, and accept amounts as decimal strings where noted.

Corporate

  • Card issuance v3 — POST /api/v3/cards/virtual and POST /api/v3/cards/plastic accept design, card_program and payment_system, and require CardSu or CardCreate.
    GET /api/v3/cards/config returns the corporation's order configuration. GET /api/v3/cards and GET /api/v3/cards/{cardId} read cards across chains.
  • Card fields — card_data.design, card_data.card_program and card_data.region on every card read.
  • Exact amounts — *_precise with decimals on wallets, FX estimates, card fees, delivery methods,
    activity amounts and statements.
  • Permissions — POST /api/v1/wallets/global can be granted through AccountSu, AccountCreate orAccountManage.
  • FedNow deposits — activating Ach adds FedNow details 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) — Cancelled no longer appears; cancelled movements read Failed.
    • A card purchase refunded or reversed in full reads Failed; a partial refund stays Completed.
    • A card purchase stays Pending until its debit settles.
    • Card fees are reported in fee_amount instead of being folded into rate, and card transactions
      carry rrn.
  • Card transfer estimate — the fee is reported per token. Top-level fee_amount is deprecated and
    always 0.
  • Corridor quotes — SEPA and Faster Payments quotes include a fee in the debited amount.

Requirements

  • In Signature mode, a payout without transaction_authorization is refused with 401. Read the mode from GET /api/v1/config before 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.

Documentation