Payment Instruments

A Payment Instrument is a tokenized card, digital wallet, or bank account. It is the source of a Transfer. Raw card data never touches your servers.

Tokenize in the browser

In production, collect card details with yusker.js hosted fields. The card is tokenized client-side and you receive a single-use token (TK…) — the PAN never reaches your backend, keeping you out of PCI cardholder-data scope. Apple Pay, Google Pay, and Interac produce tokens the same way.

const form = Yusker.tokenizationForm({ container: "#card" });
const { token } = await form.submit();   // -> "TKxxxx" (single-use)
// POST { token } to your backend, then exchange it for a Payment Instrument.

Exchange a token for an instrument

POST/v1/payment_instruments

Create a Payment Instrument from a token (or, in sandbox, a test card).

`type` enumrequired	TOKEN in production; PAYMENT_CARD for sandbox test cards.
`token` stringoptional	The single-use token from yusker.js (type=TOKEN).
`identity` stringrequired	The buyer Identity this instrument belongs to.

curl -u "$YUSKER_KEY" "$YUSKER_BASE/payment_instruments" \
  -H "Content-Type: application/json" \
  -d '{ "type": "TOKEN", "token": "TKxxxx", "identity": "IDbuyer" }'
# -> { "id": "PIxxxx", "brand": "VISA", "last_four": "0006" }

Reuse for card-on-file

A Payment Instrument is reusable. Save it against a diner's Identity to power one-tap re-orders and the Yusker Pay wallet; the network Account Updater keeps expired cards current automatically.

Card-present

For in-person taps, a certified terminal captures and encrypts the card on-device (P2PE) and produces a Payment Instrument without the PAN ever entering your app — the card-present analog to hosted-field tokenization.

Merchants

Transfers