Skip to content

Payment flows overview

Choose how you accept card payments with Cardencer: checkout SDK, server-to-server, manual capture, saved cards or payment links.

Every Cardencer payment is a payment object created with POST /payments. What changes between flows is who collects the card, when the payment is confirmed and when funds are captured.

Choose an integration#

You want to… Use Card data touches your server?
Embed a checkout in your website Checkout SDK (web) No
Accept payments in your iOS or Android app Mobile SDK No
Charge from your backend (saved cards, MOTO, your own PCI-compliant form) Server-to-server payments Only if you send raw cards
Send a link by email, SMS or chat Payment links No
Sell on WooCommerce, PrestaShop, Magento, Shopware or OpenCart Plugins No
  1. Your server creates the payment with your secret key and returns its client_secret to the browser.
  2. The checkout SDK collects the card in a Cardencer-hosted iframe and confirms the payment.
  3. If the issuer requires it, the SDK runs 3D Secure.
  4. The customer is redirected to your return_url; your server receives a webhook.

Card data goes straight from the customer to Cardencer, which keeps you in the lightest PCI DSS scope (SAQ A).

Payment patterns#

Instant payment (automatic capture)#

Authorize and capture in one step. The right choice for most checkouts. Final status: succeeded. See Instant payment.

json
{ "amount": 4900, "currency": "EUR", "capture_method": "automatic" }

Manual capture#

Authorize now, capture later, for example when you ship. The payment waits in requires_capture until you call POST /payments/{payment_id}/capture. See Manual capture.

json
{ "amount": 4900, "currency": "EUR", "capture_method": "manual" }

Decoupled create, update and confirm#

For checkouts where the basket changes, create the payment early, update it as the customer edits their order, and confirm at the end:

Step Endpoint
Create POST /payments
Update amount, customer or addresses POST /payments/{payment_id}
Confirm POST /payments/{payment_id}/confirm (the SDK does this for you)
Capture, if manual POST /payments/{payment_id}/capture

3D Secure#

Strong Customer Authentication applies to most EU card payments. Cardencer runs 3DS2 automatically when the issuer requires it; set "authentication_type": "three_ds" to always request it. The status goes requires_customer_action → succeeded. See 3D Secure / SCA.

Saved cards and recurring payments#

Pass a customer_id and setup_future_usage to save the card on the first payment, then charge it later with the returned payment_method_id. See Saved cards & recurring.

Statuses#

Terminal statuses need no further action: succeeded, failed, cancelled and partially_captured. Anything else is in progress. Always confirm the final status from your server, through a webhook or GET /payments/{payment_id}, before you fulfil an order.

Capture method What it does
automatic Default. Authorize and capture together.
manual Authorize now, capture once later (full or partial).
manual_multiple Authorize now, capture several times up to the authorized amount.

See the Payments API reference for every field.