Worldpay (Access) connector
Your Silux Chat bot answers “where’s my parcel?” from Worldpay (Access): the customer gives their tracking number and gets the live status and courier — no verification needed, nothing personal shown.
Good to know: Access Worldpay keeps no customer records; the bot looks a payment up by your transaction reference (payments since 25 June 2024).
What your bot can do with Worldpay (Access)
Delivery and tracking
Looks a parcel up in Worldpay (Access) 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 Worldpay (Access) as an administrator to create the key.
Step 1 — in Worldpay (Access)
- 1Worldpay Dashboard
- 2Developer
- 3API credentials
- 4create credentials with Payment Queries access
- 5copy the username and password.
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 Worldpay (Access) lets you create a restricted one.
Step 2 — in Silux Chat
- 1Open Dashboard → Integrations → Connectors and search for “Worldpay (Access)”.
- 2Fill in:
Field Example Stored API username •••••••• Encrypted API password •••••••• Encrypted - 3Press Connect & test. The platform makes a real, read-only call to Worldpay (Access) with a made-up customer and shows a tick or a cross for each capability, with Worldpay (Access)’s exact error if something is refused.
- 4If your bot has no parcel tracking yet, Track My Parcel is switched on automatically when the tracking test passes; otherwise press Use for tracking to make Worldpay (Access) the one your bot uses.
Worldpay (Access) identifies API users with a key-and-secret (or username-and-key) pair, sent with HTTP Basic authentication over HTTPS.
How customer verification works
Tracking needs no verification. A customer who gives their own tracking number hears only the parcel’s status and courier — the same thing Worldpay (Access)’s public tracking page shows — and only when Worldpay (Access) holds a parcel with exactly that number. Looking up an order by its order number needs the customer to be verified first.
Worldpay (Access) holds no customer records that the platform can match by name and email, so this connector cannot verify customers by itself. It is tested when you connect it and re-checked every day. To plan how its data should reach your customers alongside your verification route — a connector that can look customers up, or your own Account Connect endpoints — email support@siluxcall.co.uk.
What the bot can and cannot see
Can see (after verification)
No customer records — tracking only.
Tracking, without verification: order number, status, tracking number and courier — only for the tracking number the customer gave.
Only these standard fields are mapped from Worldpay (Access)’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 Worldpay (Access).
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 Worldpay (Access)’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 Worldpay (Access) endpoints this connector reads, relative to https://access.worldpay.com. Values in braces come from the settings you enter.
| Capability | Request | Standard fields returned |
|---|---|---|
| Delivery and tracking | GET/paymentQueries/payments | order_number, status, placed, total, currency |
Test level: Documented-API tested. Each capability is run automatically against Worldpay (Access)’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 Worldpay (Access) 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 Worldpay (Access) record, and that the surname matches. |
| A capability shows a cross but others work | That permission wasn’t granted in Worldpay (Access), or your Worldpay (Access) plan doesn’t include that part of the API. Grant it and press Test. |
| “the vendor kept rate-limiting the request” | Worldpay (Access) returned “too many requests” three times in a row. The platform already waits and retries automatically (up to 10 seconds, as Worldpay (Access) asks); if it persists, ask Worldpay (Access) about your API quota. |
| Results are empty for a verified customer | The records exist under a different email or customer record in Worldpay (Access), or none are recent. Check the customer’s record in Worldpay (Access) directly. |
Full error reference: Troubleshooting & error reference.
Frequently asked questions
Is the Worldpay (Access) connection read-only?
Yes. Every request Silux Chat makes to Worldpay (Access) is a look-up; none creates, changes or deletes anything in Worldpay (Access). Give the key or sign-in read-only permissions wherever Worldpay (Access) offers them.
Do I need a developer to connect Worldpay (Access)?
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 Worldpay (Access) straight away and shows exactly which features work.
How does the bot know it is really my customer?
For tracking it doesn’t need to: the customer gives their own tracking number and hears only the status and courier. Worldpay (Access) can’t verify customers by itself, so looking an order up by its order number needs verification through another connector or your own Account Connect endpoints.
What happens if my Worldpay (Access) 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 Worldpay (Access) connector been tested?
It is Documented-API tested: every capability is run automatically against Worldpay (Access)’s documented example responses and must produce the standard fields. When you connect, it is tested again with a real call to your own Worldpay (Access) account before your bot uses it.
Other payments connectors
Braintree
Recognise and verify customers · Orders and order status
Checkout.com
Recognise and verify customers · Delivery and tracking
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
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.