Recurring billing · on request
Stored credentials, network tokens and mandates for subscriptions and instalments.
Save a payment method once, with the customer's consent, and charge it again as a merchant-initiated transaction without a second authentication. Available on request while the subscriptions API is in development.
What it does
- 01
Network tokens for cards, so a reissued card keeps working and authorization rates hold.
- 02
SEPA and open-banking mandates for account-to-account collections.
- 03
Merchant-initiated transactions flagged correctly for SCA, with the exemption recorded on every payment.
In practice
Recurring billing runs on the same payment object.
Merchant-initiated transactions and stored credentials are enabled per account; the API surface is the one you already know.
# Create with capture_method "manual"
curl https://cleared-pay.com/api/v1/payments -H "Authorization: Bearer cp_sk_test_..." \
-H "Content-Type: application/json" \
-H "Idempotency-Key: 8b1f0d3a-2c4e-4f6a-9b8c-0d1e2f3a4b5c" \
-d '{"amount":10000,"currency":"eur","reference":"ORDER-10440","capture_method":"manual","payment_method":{"type":"card","token":"tok_..."}}'
# Later: capture 6,000 of the 10,000; the remaining authorisation is released
curl https://cleared-pay.com/api/v1/payments/pay_.../captures -H "Authorization: Bearer cp_sk_test_..." \
-H "Content-Type: application/json" \
-d '{"amount":6000}'Payment methods
Methods this product carries.
Tell us what you're building. We'll tell you what we can do.
A short form, a real underwriter, and a clear answer on methods, pricing and timing.