Introduction
How Cardencer works: one API for card payments, a checkout SDK that keeps card data off your servers, and signed webhooks.
Cardencer lets EU-registered businesses accept Visa, Mastercard, Apple Pay and Google Pay through a single integration. Cardencer operates the gateway and configures the acquirer for your account, so you only integrate with Cardencer.
What you can build#
- Online checkout: embed the checkout SDK in your website, or use the mobile SDKs in your app. Card details go straight from the customer's browser or phone to Cardencer.
- Server-side payments: create and confirm payments from your backend with the REST API, for example to charge a saved card.
- No-code payments: send a payment link by email or chat.
- Ecommerce plugins: install the WooCommerce, PrestaShop, Magento, Shopware or OpenCart plugin, paste your keys and start selling.
How a payment works#
- Your server creates a payment with
POST /paymentsand your secret key. Cardencer returns apayment_idand aclient_secret. - Your frontend loads the checkout SDK with your publishable key and the
client_secret. The customer enters their card. - The SDK confirms the payment. If the issuer asks for 3D Secure, the SDK shows the challenge.
- Cardencer sends a webhook to your server and the customer returns to your
return_url. - Your server checks the final status with
GET /payments/{payment_id}or the webhook, then fulfils the order.
Keys#
You use three values from the dashboard (API keys page):
| Value | Example | Where it lives |
|---|---|---|
| Secret API key | snd_… / prd_… |
Your server only. Sent in the api-key header. |
| Publishable key | pk_snd_… / pk_prd_… |
Your website or app. Initialises the SDK. |
| Profile ID | pro_… |
Your website or app. Identifies your business profile; not a credential. |
Read Authentication for the details.
Amounts and currencies#
Amounts are integers in the currency's minor unit: 4900 with "currency": "EUR" is EUR 49.00. Currencies use ISO 4217 codes.
Payment statuses#
| Status | Meaning |
|---|---|
requires_payment_method |
Created, waiting for card details. |
requires_confirmation |
Card details attached, waiting for confirmation. |
requires_customer_action |
The customer must complete 3D Secure. |
processing |
The acquirer is still working on it. |
requires_capture |
Authorized, waiting for you to capture. |
succeeded |
Funds captured. |
failed |
Declined or errored. Read error_code and error_message. |
cancelled |
Cancelled before capture. |
Next: run the quickstart.