Manage payment methods
Save, update, and remove customer payment methods in the VINR vault.
Saving a payment method to a customer record lets you charge them later without asking them to re-enter their details — essential for subscriptions, one-click reorders, and off-session charges. VINR vaults the payment method in its PCI-compliant secure storage; you store only the pm_... identifier.
The payment method vaultAsk
When a customer's payment method is saved, VINR stores the sensitive data (card number, expiry, etc.) and returns a reusable PaymentMethod ID. You attach this ID to a Customer record to associate it with a specific person.
Customer (cus_...)
└── PaymentMethod (pm_...) ← safe to store, reuse, and pass in API calls
└── Card data ← held in VINR's PCI vault, never exposed in the APINever store raw card numbers. pm_... IDs are safe to store — they reference tokenized data held entirely in VINR's PCI-compliant vault.
Reusable vs single-use methodsAsk
Not all payment methods can be saved for reuse:
| Method | Reusable | Notes |
|---|---|---|
| Cards | Yes | Can be charged unlimited times after saving |
| SEPA Direct Debit | Yes | Requires mandate acceptance at setup |
| iDEAL, Bancontact | No | Single-use redirect; VINR generates a reusable SEPA mandate after the first use |
| Bank transfers | No | Each transfer is a separate instruction |
| Meal vouchers | No | Physical voucher cards are not stored |
In this sectionAsk
Save a payment method
Save during a payment or without charging using a Setup flow.
Update & replace
What can be updated on a saved method and when to re-collect.
Automatic card updates
How VINR refreshes saved card details when a bank re-issues a card.
Faster checkout
One-tap checkout for returning customers with saved payment methods.
Last updated on
