Tokenised payments
Save a card once. Charge it when your customer agrees.
Your customer chooses to keep their card on the hosted checkout. Payable keeps the card and you get a token for it, never the number. Charge it later for what they agreed to, from your server or your dashboard.
- Card numbers on your servers
- None
- Charge from
- Your server or the dashboard
- Customer's consent
- Kept with the card
How it works
The customer saves it, you charge it
The card is typed once, by the customer, on Payable's page. Everything after that uses a token.
- 1
The customer chooses to keep it
Offer to keep the card on a checkout. Nothing is kept unless the customer ticks the box, and their consent is recorded with the wording they read and the language they read it in.
- 2
Payable keeps the card
The card is stored by Payable, not by you and not by us. You receive a card id with the last four digits and the month it expires.
- 3
Charge it later
Charge the card without the customer present, for something they agreed to: from your server with the API, or from the dashboard.
- 4
Remove it when asked
Delete a card when the customer asks or cancels. It stops working at once, and its token is deleted at Payable.
What it is for
Payments the customer does not have to repeat
Repeat orders and top ups
One tap reorders, top ups and refills, charged to the card the customer already saved.
Billing you run yourself
Usage, instalments or monthly fees on your own schedule, with an idempotency key so a retry never charges twice.
Deposits on a saved card
Place a hold on a saved card, then capture or release it, without asking the customer to pay again.
Pre-authorisationSubscriptions
Our subscriptions keep the card at the first payment and charge it every period, retrying a decline for you.
Subscriptions
In your dashboard
Every saved card, and every charge made with it
Tokenised payments lists the cards your customers kept, live and sandbox apart, with the charges made on each.
- Charge a card for an amount and a description, or place a hold on it instead.
- Live charges and holds ask for your password and a one time code.
- See when the customer agreed to keep the card.
- The owner, admins and support can charge a card.
Safe by design
Card numbers never reach your servers
The card stays with Payable
The customer types the card on Payable's page. You and Payments.lk only ever hold a token and the last four digits.
Consent you can show
Each card carries when the customer agreed, in which language, and which wording they read. It stays readable after the card is removed.
The bank's check, once
The customer passes their bank's check on the first payment. A later charge is made without them, so a bank that insists on a check declines it, and you ask the customer to save the card again.
Subscriptions run on saved cards
A subscription keeps the card at its first payment and charges it every period. Customers change their card in the customer portal, and are told before the card they pay with expires.
Availability and price
On in test mode today
Test mode: every account
Save, charge, hold and remove test cards once you have submitted your application. Every sandbox account is already on Payable's Advanced plan.
Live: switch it on
Once your account is live, switch saved cards on under Business settings. It moves your account to Payable's Advanced plan, which carries its own monthly fee and a fee for each card saved. The dashboard shows both before you confirm.
Each charge
A charge on a saved card is a card payment at your plan's rate, from 2.29%.
Everything else
One-time checkouts, payment links and checkout pages work on every plan, with or without saved cards.
For developers
saveCard on a checkout, then one call to charge
Set saveCard on a checkout and keep the card id that card.saved brings. Charge it with one call and an idempotency key per billing period, so a retry never charges twice.
// The first payment: the checkout offers to keep the card.
const checkout = await lk.checkouts.create({
amountCents: 250000, // Rs. 2,500.00
description: "First month of your coffee subscription",
customer: { name: "Ruwan Silva", email: "ruwan@example.lk" },
saveCard: true,
successUrl: "https://yourshop.lk/account",
});
// card.saved brings the card id: keep it. Never a card number.
// Next month, charge it, once per period however often you retry:
const payment = await lk.cards.charge(
cardId,
{ amountCents: 250000, description: "October coffee subscription" },
{ idempotencyKey: "sub-1042-2026-10" },
);Ready to keep your customers' cards, safely?
Start your application and try saved cards in test mode today.