This feature is exclusive to a select number of partners on demand.
How it works
1
Create a binding
Make a first payment with a unique
client_id. The customer completes checkout normally, and their payment method is saved for future use. See Create Binding.2
Pay with the binding
For subsequent transactions, send the
binding_id, client_id, and cvc along with the payment amount. No checkout redirect needed (except for 3DS). See Pay with Binding.3
Verify the payment
Use the standard Verify Payment endpoint to confirm the transaction status.
Use cases
Recurring payments
For subscriptions, memberships and scheduled billing use the dedicated Recurring Payments API: Flouci debits the customer’s wallet on each cycle without the customer present. Pay with Binding requires the card’s
cvc on every charge, so it cannot debit a saved card unattended.One-click checkout
Returning customers pay instantly without re-entering payment details or being redirected.
In-app purchases
Native mobile experiences where payments happen seamlessly within your app.
Saved payment methods
Let customers save their preferred payment method for faster future transactions.
