Zettle by PayPal connector
Connect Zettle by PayPal to Silux Chat with a read-only connection for orders and order status. It is tested with a real call when you connect it and re-checked every day.
Good to know: Zettle's Purchase API has no customer records; the bot can list recent till purchases only.
What your bot can do with Zettle by PayPal
Orders and order status
Reads a verified customer’s recent orders from Zettle by PayPal — order number, date, status and total, plus tracking where Zettle by PayPal records it.
Customers ask: “Where is my order?” · “Has my last order been sent?”
Connected and tested when you connect Zettle by PayPal, but the bot does not answer customers from it: Zettle by PayPal can’t prove who is asking, and these records are personal. Email support@siluxcall.co.uk to discuss using it.
Set it up
Most businesses finish in under ten minutes. You need to be able to sign in to Zettle by PayPal as an administrator.
Step 1 — in Zettle by PayPal
Connect with Zettle (OAuth) — Silux Chat asks for read access to your purchases.
Permissions (scopes) requested — read-only:
READ:PURCHASELeast access: grant only the read permissions named above. Never use an owner or full-admin key where Zettle by PayPal lets you create a restricted one.
Step 2 — in Silux Chat
- 1Open Dashboard → Integrations → Connectors and search for “Zettle by PayPal”.
- 2Press Sign in with Zettle by PayPal. The platform makes a real, read-only call to Zettle by PayPal with a made-up customer and shows a tick or a cross for each capability, with Zettle by PayPal’s exact error if something is refused.
There is no key to copy. You press “Sign in with Zettle by PayPal”, approve read-only access on Zettle by PayPal’s own page, and are returned to your dashboard. The access token is stored encrypted and refreshed automatically before it expires.
How customer verification works
Zettle by PayPal 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)
Nothing — see the verification section above.
Only these standard fields are mapped from Zettle by PayPal’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
Sign-in tokens 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 Zettle by PayPal.
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 Zettle by PayPal’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 Zettle by PayPal endpoints this connector reads, relative to https://purchase.izettle.com. Values in braces come from the settings you enter.
| Capability | Request | Standard fields returned |
|---|---|---|
| Orders and order status | GET/purchases/v2 | order_number, placed, status, total, currency |
Test level: Documented-API tested. Each capability is run automatically against Zettle by PayPal’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 sign-in was revoked or has expired, or it lacks a read permission this connector needs. Sign in with Zettle by PayPal again. |
| “Silux Chat’s Zettle by PayPal app is not registered yet” | Our sign-in app with Zettle by PayPal isn’t available yet; our team is notified automatically. Email support@siluxcall.co.uk for timing or alternatives. |
| 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 Zettle by PayPal record, and that the surname matches. |
| A capability shows a cross but others work | That permission wasn’t granted in Zettle by PayPal, or your Zettle by PayPal plan doesn’t include that part of the API. Grant it and press Test. |
| “the vendor kept rate-limiting the request” | Zettle by PayPal returned “too many requests” three times in a row. The platform already waits and retries automatically (up to 10 seconds, as Zettle by PayPal asks); if it persists, ask Zettle by PayPal about your API quota. |
| Results are empty for a verified customer | The records exist under a different email or customer record in Zettle by PayPal, or none are recent. Check the customer’s record in Zettle by PayPal directly. |
Full error reference: Troubleshooting & error reference.
Frequently asked questions
Is the Zettle by PayPal connection read-only?
Yes. Every request Silux Chat makes to Zettle by PayPal is a look-up; none creates, changes or deletes anything in Zettle by PayPal. Give the key or sign-in read-only permissions wherever Zettle by PayPal offers them.
Do I need a developer to connect Zettle by PayPal?
No. You sign in with Zettle by PayPal in Dashboard → Integrations → Connectors and press “Sign in with Zettle by PayPal”. The platform makes a real call to Zettle by PayPal straight away and shows exactly which features work.
How does the bot know it is really my customer?
Zettle by PayPal holds no customer records the platform can search, so it cannot verify customers by itself. See the verification section on this page, or email support@siluxcall.co.uk to plan the right set-up.
What happens if my Zettle by PayPal 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 Zettle by PayPal connector been tested?
It is Documented-API tested: every capability is run automatically against Zettle by PayPal’s documented example responses and must produce the standard fields. When you connect, it is tested again with a real call to your own Zettle by PayPal 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.