Payment Methods

Vault and manage saved payment methods.

Use a Collect.js token or raw card details to vault a card, then charge it later via POST /charges. On Paysio Debit & Payouts workspaces you can also save bank accounts — usable for ACH debits and as payout destinations.

Add Payment Method

Save a payment method to a customer. If the customer has no vault yet, one is created automatically. Accepts a paysio.js token (from paysio.createToken()), raw card details, or — on bank-capable workspaces (Paysio Debit & Payouts or NMI) — bank account details with type 'bank_account'.

POSThttps://paysio.com/api/v1/customers/:id/payment-methods

Authorizations

Authorizationstringheaderrequired

Secret key (sk_*). Prepend your key with Bearer, e.g. Bearer sk_test_your_secret_key.

Body

typestring

"card" (default) or "bank_account" (Paysio Debit & Payouts or NMI workspaces)

payment_tokenstring

Token from paysio.createToken() (card)

cc_numberstring

Card number (use payment_token instead when possible)

cc_exp_monthstring

Expiry month (01-12), required with cc_number

cc_exp_yearstring

Expiry year (e.g. 2028), required with cc_number

routing_numberstring

9-digit routing number, required with type "bank_account"

account_numberstring

Bank account number (4-17 digits), required with type "bank_account"

account_typestring

"checking" (default) or "saving", with type "bank_account" (only used by NMI)

account_holder_typestring

"personal" (default) or "business", with type "bank_account" (NMI eCheck only; ignored by Debit & Payouts)

descriptionstring

Optional label for a bank account (e.g. "Payroll account")

List Payment Methods

List a customer's saved payment methods, with masked details. Treat id as an OPAQUE string — pass it as payment_method_id to POST /charges, /payouts, /account-checks and /three-ds/authenticate, but never parse or build it yourself. On accounts using the Paysio vault (the default for cards on NMI and Debit & Payouts) ids look like 'vault_…' and processor is 'paysio_vault'; legacy methods keep their gateway instrument id. Both forms are accepted everywhere. payout_eligible tells you whether a method can receive a payout — banks and debit/prepaid cards qualify once Debit & Payouts is enabled, while a known CREDIT card returns false (push-to-card only settles on debit rails; unclassified cards default to true and are re-verified at send time). Paysio-vaulted methods are gateway-agnostic, so a card saved while charging on NMI can still be paid out. Lists can mix cards and bank accounts (type 'bank_account').

GEThttps://paysio.com/api/v1/customers/:id/payment-methods

Authorizations

Authorizationstringheaderrequired

Any API key. Prepend your key with Bearer, e.g. Bearer sk_test_your_secret_key.

Delete a payment method

Remove a saved payment method from a customer's vault.

DELETEhttps://paysio.com/api/v1/customers/:id/payment-methods/:billingId

Authorizations

Authorizationstringheaderrequired

Secret key (sk_*). Prepend your key with Bearer, e.g. Bearer sk_test_your_secret_key.