Checkout.com connector
Your Silux Chat bot verifies customers against Checkout.com, then answers questions about their customer records from your live data. Customers can also track a parcel by its tracking number, without verifying.
What your bot can do with Checkout.com
Recognise and verify customers
Finds the customer in Checkout.com by the email address or mobile number they give, checks their name and one more detail, then sends a one-time code to the contact details Checkout.com holds. Nothing personal is shared until the code is entered.
Customers ask: “I want to check my account — it’s Jane Smith, jane@example.com”
Delivery and tracking
Looks a parcel up in Checkout.com by the tracking number the customer gives and answers with its status and courier — no verification needed, and nothing personal is returned. Looking an order up by its order number needs the customer to be verified first.
Customers ask: “What’s my tracking number?” · “Has my parcel been delivered?”
Answered by the bot’s Track My Parcel tool: by tracking number for anyone (status and courier only), by order number only for a verified customer and only for their own order.
Set it up
Most businesses finish in under ten minutes. You need to be able to sign in to Checkout.com as an administrator to create the key.
Step 1 — in Checkout.com
- 1Checkout.com Dashboard
- 2Developers
- 3Keys
- 4Create a secret key with Customers and Payments read scopes
- 5copy it.
Least access: grant only the read permissions named above (customers, orders, invoices, bookings or tickets — whichever this connector uses). Never use an owner or full-admin key where Checkout.com lets you create a restricted one.
Step 2 — in Silux Chat
- 1Open Dashboard → Integrations → Connectors and search for “Checkout.com”.
- 2Fill in:
Field Example Stored Secret key (sk_…) •••••••• Encrypted - 3Press Connect & test. The platform makes a real, read-only call to Checkout.com with a made-up customer and shows a tick or a cross for each capability, with Checkout.com’s exact error if something is refused.
- 4If this is your first way of verifying customers it is switched on automatically; otherwise press Use to verify customers. The platform then runs its chained test (verify → code → account → orders → invoices) with the built-in test customer — no real person is contacted. Track My Parcel is added at the same time unless another connector already provides it.
You create an API or access token in Checkout.com and paste it into your dashboard. It is sent as a Bearer token on every call, over HTTPS only.
How customer verification works
- STEP 1
Customer asks
They ask about their own account. The bot asks for their full name and their email or mobile, plus one more detail such as their postcode.
- STEP 2
Found in Checkout.com
The customer is looked up in Checkout.com by email, then mobile. The surname must match exactly and the first name must match or start with the same letter, plus one more detail.
- STEP 3
Code sent
A 6-digit code goes to the mobile Checkout.com holds (by text, when your plan has SMS) or otherwise to the email it holds. The chat never chooses where it goes.
- STEP 4
Verified
The customer types the code. It is valid for 10 minutes and five wrong attempts cancel it. The verified session lasts 30 minutes.
If the details don’t match, the customer is told only that they couldn’t be matched — never which detail was wrong. If Checkout.com can’t be reached, the bot says it can’t check accounts right now rather than “no account found”. The bot is blocked in code from reading orders, invoices or bookings until verification succeeds. Full details: Customer identity verification & OTP.
What the bot can and cannot see
Can see (after verification)
Tracking, without verification: order number, status, tracking number and courier — only for the tracking number the customer gave.
- Record ID
- Name
- Email address
- Phone / mobile
Only these standard fields are mapped from Checkout.com’s responses. Everything else in the response is discarded before the bot sees it.
Never sees
- full card numbers, CVV or bank details
- passwords, security answers or login details
- records belonging to anyone other than the verified customer
- anything outside the fields listed alongside
Security
Keys encrypted at rest
Credentials are stored encrypted, shown only masked after saving, and destroyed — not just hidden — when you disconnect.
Read-only look-ups
Every capability is a look-up. The connector cannot create, change or delete anything in Checkout.com.
HTTPS only
Calls go to the vendor’s HTTPS address, redirects are not followed, and private network addresses are refused.
Injection-safe
Values a customer types are cleaned before they are placed in Checkout.com’s search, and URL-encoded in addresses.
Other customers filtered out
A row that names a different customer’s email is dropped, whatever the vendor’s search returned.
Checked daily
Connections are re-tested every day, and the owner is emailed if a working connection starts failing.
More: Security & data protection.
Technical details
For developers and IT teams: the Checkout.com endpoints this connector reads, relative to https://api.checkout.com. Values in braces come from the settings you enter.
| Capability | Request | Standard fields returned |
|---|---|---|
| Recognise and verify customers | GET/customers/{email} | id, name, email, phone |
| Delivery and tracking | GET/payments | order_number, status, placed, total, currency |
Test level: Documented-API tested. Each capability is run automatically against Checkout.com’s documented example responses and must produce the standard fields; your own connection is then tested with a real call when you connect. The bot receives these through the standard Account Connect endpoints, exactly as if you had built them yourself.
Troubleshooting
| What you see | Likely cause and fix |
|---|---|
| “the vendor refused the credentials (401)” or (403) | The key was revoked, has expired or was copied incompletely, or it lacks a read permission this connector needs. Create a fresh read-only key in Checkout.com and reconnect. |
| Customers are “not matched” although they exist | Customers are looked up by email or mobile, not postcode. Check the customer’s email or mobile is saved on their Checkout.com record, and that the surname matches. |
| A capability shows a cross but others work | That permission wasn’t granted in Checkout.com, or your Checkout.com plan doesn’t include that part of the API. Grant it and press Test. |
| “the vendor kept rate-limiting the request” | Checkout.com returned “too many requests” three times in a row. The platform already waits and retries automatically (up to 10 seconds, as Checkout.com asks); if it persists, ask Checkout.com about your API quota. |
| Results are empty for a verified customer | The records exist under a different email or customer record in Checkout.com, or none are recent. Check the customer’s record in Checkout.com directly. |
Full error reference: Troubleshooting & error reference.
Frequently asked questions
Is the Checkout.com connection read-only?
Yes. Every request Silux Chat makes to Checkout.com is a look-up; none creates, changes or deletes anything in Checkout.com. Give the key or sign-in read-only permissions wherever Checkout.com offers them.
Do I need a developer to connect Checkout.com?
No. You paste the details listed in the set-up steps in Dashboard → Integrations → Connectors and press “Connect & test”. The platform makes a real call to Checkout.com straight away and shows exactly which features work.
How does the bot know it is really my customer?
It finds the customer in Checkout.com by the email or mobile they give, checks their name and one more detail, then sends a one-time code to the mobile or email held in Checkout.com — never to one typed in the chat. The code lasts 10 minutes, five wrong attempts cancel it, and a verified session lasts 30 minutes.
What happens if my Checkout.com key is revoked or expires?
The bot tells customers it can’t check their account right now — it never pretends there are “no orders”. Connections are re-tested daily and the account owner is emailed when a working connection starts failing. Reconnect it in Dashboard → Integrations → Connectors.
How has the Checkout.com connector been tested?
It is Documented-API tested: every capability is run automatically against Checkout.com’s documented example responses and must produce the standard fields. When you connect, it is tested again with a real call to your own Checkout.com account before your bot uses it.
Other payments connectors
Braintree
Recognise and verify customers · Orders and order status
GoCardless
Recognise and verify customers · Orders and order status · Subscriptions and plans
Mollie
Recognise and verify customers · Orders and order status · Subscriptions and plans
PayPal
Recognise and verify customers · Invoices
Revolut Business (Merchant API)
Recognise and verify customers · Orders and order status
Square
Recognise and verify customers · Invoices · Orders and order status
Stripe
Account balance · Recognise and verify customers · Invoices · Orders and order status · Subscriptions and plans
SumUp
Delivery and tracking · Orders and order status
Worldpay (Access)
Delivery and tracking
Need help with your integration?
Our integration team can review your endpoints, help you choose the right connector and check a test run with you. Tell us which system you use and what you would like the bot to answer.