Payments infrastructure · EEA
Every payment method in. One cleared rail out.
Card acquiring, alternative payment methods and payouts on a single EEA-built rail — with a backoffice your finance team can actually use and an API your engineers won't fight.
No account is created — we read what you send and come back with a quote. Or read the docs →
- Sandbox in 5 minutes
- 3DS2 & SCA ready
- One dashboard for every acquirer
Rails and instruments on one integration
- Cards
- Wallets
- Instant bank transfer
- Bank debit
- Buy now, pay later
- Vouchers
- Crypto
- Payment methods
- 55cards to crypto, documented one by one
- Settlement currencies
- —listed when the acquirer contract is signed
- Settlement cycle
- T+nstated per agreement, never assumed
- API uptime
- —published after 90 measured days
Products
Everything between the checkout and the bank.
One integration, one status model and one portal — whichever rail the payment takes.
- Card acquiringVisa, Mastercard and the local schemes that matter, with authorization routing built to say yes more often.
- Alternative payment methodsWallets, open banking, BNPL, vouchers and crypto. One integration, every rail your customers already trust.
- Hosted checkoutA payment page we host, brand to you, and keep in PCI scope so your servers never touch a card number.
- Payouts and mass paymentsSend money out as easily as you take it in. Single or bulk, to cards or bank accounts.
- Fraud and riskVelocity rules, BIN and device lists, and a manual review queue — tuned per merchant, not per industry stereotype.
- Multi-currency settlementCharge in their currency, settle in yours, and see exactly what each transaction cost you.
Payment methods
55 ways to be paid. One way to see them.
Cards, wallets, bank transfer, buy now pay later, vouchers and crypto — each documented with its flow, settlement timing and refund support.
Industries
Written by people who have run payments for your industry.
Each page starts with the three payment problems the vertical actually has, then the capabilities and methods that answer them.
- iGamingDeposits that convert. Withdrawals that arrive.
- Crypto and web3On-ramp, off-ramp, and the settlement in between.
- Trading and forexFunding in, withdrawals out, same day.
- E-commerce and retailLocal methods, routing that says yes, statements your finance team can close.
- Digital goods and subscriptionsRecurring billing that keeps working when the card changes.
- MarketplacesTake payments in, pay sellers out, keep one ledger.
The backoffice
One dashboard. Every acquirer.
Transactions, settlements, fees, disputes and API keys across every connection you run — in one place, with the numbers reconciled. Your finance team stops exporting spreadsheets from four different portals.
Integration
One request. Every method.
Create a payment, get a status, receive a signed webhook. Test cards and a full sandbox from the moment your account opens — no sales call needed to start building.
Developers · API keys
- Test secret key
- cp_sk_test_••••••••4f2a
- Test publishable key
- cp_pk_test_••••••••9c1e
Keys show once at creation and can be rolled with a grace window. Every request is logged with its request id.
# 1. Tokenise a test card (hosted fields do this in the browser; the sandbox tokenizer does it for you)
curl https://cleared-pay.com/api/v1/sandbox/tokens \
-H "Authorization: Bearer cp_sk_test_..." \
-H "Content-Type: application/json" \
-d '{"type":"card","number":"4242424242424242","exp_month":12,"exp_year":2031,"cvc":"123"}'
# 2. Create the payment with the token
curl https://cleared-pay.com/api/v1/payments \
-H "Authorization: Bearer cp_sk_test_..." \
-H "Idempotency-Key: 4f0a2c6e-9b31-4c0d-9a7e-1f2b3c4d5e6f" \
-H "Content-Type: application/json" \
-d '{
"amount": 2000,
"currency": "eur",
"reference": "ORDER-10432",
"payment_method": { "type": "card", "token": "tok_..." },
"return_url": "https://merchant.example/return"
}'Service
Someone answers
A named account manager, a real underwriter, and support that has seen your integration before. Not a ticket queue that closes at five.
- PCI DSSAssessment scheduled; the attestation and its date are published here when issued.
- 3-D Secure 2 and SCABuilt in: exemptions, challenge flows and a sandbox that exercises both.
- ISO 27001Certification in progress; the certificate and its scope are published when granted.
- Scheme registrationsVisa and Mastercard programme registrations are listed once obtained.
Case studies
Stories appear here when merchants agree to tell them.
We publish a case study only with the merchant's written consent and their own numbers. Until then these slots stay visibly empty.
Placeholder — Consolidating four acquirer portals into one settlement view.
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.
Resources
Plain answers to the questions payments people actually ask.
- 6 min read3-D Secure 2, explainedWhat 3-D Secure 2 does, when SCA applies, which exemptions exist, and what each means for your approval rate.
- 6 min readChargeback or refund: what the difference costs youA refund is a decision you make; a chargeback is a decision made for you. The fees, the ratios and the timelines that follow from that.
- 6 min readWhat a rolling reserve actually isA percentage of each settlement, held for a window, released as it ages out. The mechanics, the reasons, and what you should ask for.