Push to Card

Before You Start

Read the following guides before proceeding:

---

Push to card credits an external Visa or Mastercard over OCT rails, debiting a token balance from the
corporation wallet. It is the shortest payout path a corporation has: no bank account to activate, no
corridor to select, no IBAN to collect — a card identifier and an amount.

The destination card is never handled in clear text by this API. It is tokenized in Wirex's
PCI-compliant environment, and the resulting identifier is stored as a Card payment detail on a
recipient. That identifier is what the transfer names.

Transfers follow the estimate-then-execute pattern used everywhere else in the Corporate API: the
estimate quotes the debit across the tokens you nominate and returns an estimation_id; execution
names the token to debit.

Both endpoints require CardSu. A role designed for payments — TransactionCreate — does not reach
them.

Transfer Flow (Simplified)

Detailed documentation available in Card Transfer.

sequenceDiagram
    participant App as Your App
    participant PCI as Wirex PCI
    participant Corp as Wirex Corporate API

    Note over App,Corp: Card registration, once per card
    App->>PCI: 1. Tokenize the card
    PCI-->>App: card identifier
    App->>Corp: 2. POST /api/v2/recipients — type Card
    Corp-->>App: payment_details.id

    Note over App,Corp: Each transfer
    App->>Corp: 3. POST /api/v1/cards/transfer/estimate
    Corp-->>App: estimation_id, estimated_amounts[]
    App->>Corp: 4. POST /api/v1/cards/transfer
    Corp-->>App: transaction id
    Corp->>App: POST /v2/webhooks/activities

---

Guides