These three are listed alongside the local providers, but they are not a substitute for one: each only onboards businesses in the countries it supports. Use them where you already have an account, or where your business is registered somewhere they operate.
Stripe
Available in every market we serve, for businesses that hold a Stripe account. Three fields, all from the developers section of your Stripe dashboard.
-
1
Open the Stripe dashboard as the account owner
Check the top of the screen for whether you are in test or live mode — the keys are different.
-
2
Copy the secret key
In the API keys section. It is revealed once; if you have lost it, roll a new one.
-
3
Copy the publishable key
Required: it is what draws the card form, Apple Pay and Google Pay into your menu instead of sending guests to a Stripe page.
-
4
Add a webhook endpoint
Paste our callback address as the endpoint URL, choose the events below, and copy the signing secret it gives you back.
| Field in TapTime | Where it comes from |
|---|---|
| Secret key | Stripe dashboard → Developers → API keys. Secret. Starts sk_. |
| Publishable key | Same page. Not secret. Starts pk_. |
| Webhook signing secret | Given when you create the webhook endpoint. Secret. Starts whsec_. |
Select these events on the endpoint: payment_intent.succeeded, payment_intent.payment_failed, payment_intent.canceled and charge.refunded. Selecting every event also works and costs you nothing. If you connected Stripe before we asked for the publishable key, add checkout.session.completed as well — that is the older, redirected flow.
Square
Square is a good fit where you already use Square hardware in the venue. The location id ties online payments to the same location as your terminal.
| Field in TapTime | Where it comes from |
|---|---|
| Access token | Your application in the Square developer dashboard. Secret. |
| Location ID | The location in your Square account these payments belong to. |
| Application ID | Optional. From your application in the Square developer dashboard. Lets guests pay by card, Apple Pay or Google Pay inside the menu instead of on a Square page. |
| Webhook signature key | Optional. Given when you add a webhook subscription. |
If you add a webhook subscription, subscribe it to payment.created and payment.updated. It is optional: every payment is re-read from Square before it is believed, so the notification is a second lock rather than the only one.
PayPal
Two fields, from an app you create in the PayPal developer dashboard. Note that PayPal does not onboard merchants in several of our markets — Türkiye among them — so check that your country is supported before you plan around it.
| Field in TapTime | Where it comes from |
|---|---|
| Client ID | The app in your PayPal developer dashboard. |
| Client secret | Issued with it. Secret. |
Local or international?
| Choose local when | Choose international when |
|---|---|
| Your guests pay with local cards, which is almost always | You already run on Stripe or Square and want one dashboard |
| You want the best rate available in your market | You take payments from abroad in several currencies |
| Your bank has already offered you a terminal | No local provider will onboard your entity |
Sering ditanyakan
Is Stripe available in my country?
Stripe supports businesses in many countries but not all of ours. Check on their site with your country of registration before choosing it.
Do I need the webhook secret?
It is optional and worth adding. Without it, payments are still verified — we re-read them from the provider — but the signature is a useful second lock.
Can guests pay with a PayPal balance?
That depends on what your PayPal merchant account is enabled for; TapTime simply hands the payment to PayPal.
Terima kasih — itu membantu kami memperbaiki panduan ini.
Tulis kepada kami dan sebutkan halaman yang Anda buka. Setiap pesan dibaca orang sungguhan dan dijawab dalam bahasa yang Anda pakai.
Tulis kepada kami