What can you do with Core Checkout?
Core Checkout lets you accept payments on your own website or app through our API, with a payment page hosted by Core. There are three ways to collect a payment.
- One-shot payment. Your customer is redirected to the payment page, enters their payment details and pays. Use POST /transactions.
- Register a card, then charge it when you decide (MIT). You first register the customer’s card, without any payment. The CVV is always requested at this step, and 3D Secure may apply. You then charge the saved card from your server whenever you decide, with no customer present: a no-show fee, a top-up when a balance runs out, usage-based billing, or your own recurring schedule. At this stage, a CVV or 3D Secure request is very rare. Use POST /cards/register, then POST /transactions/rebill.
- Subscriptions (coming soon). A dedicated Subscription module will manage recurring subscriptions for you. Until it is available, recurring payments can run through option 2 with your own scheduler.
Which payment method works with which option?
One-shot | Register a card + MIT | Subscriptions | |
|---|---|---|---|
Card | ✅ | ✅ | Coming soon |
Apple Pay | ✅ | ❌ | ❌ |
Carlo App | ✅ | ❌ | ❌ |
Apple Pay cannot be registered as a reusable card, and a Carlo App payment is always approved by the customer in the app. Only bank cards can be saved and charged later.
Good to know
In every case, the webhook callback is the source of truth for the payment result, not the redirect.
Refunds: card and Apple Pay payments are cancelled through the API (full amount, within 3 days). Carlo App payments are refunded from the Carlo Business dashboard, within 30 days.
See also: CIT and MIT: what changes for a recurring payment?
Updated on: 28/10/2026