Tap to Pay
Tap to Pay on iPhone uses one card-present provider for the whole account. Devices with Tap to Pay enabled all follow this setting.
SumUp
Connect a SumUp merchant account for transaction history and Tap to Pay setup. Ask SumUp to enable the payments OAuth scope on TabTap’s app, then reconnect so iPhones can log in without a SumUp password.
Connected to SumUp.
Reconnect after SumUp enables the payments scope (and after that scope is added back to TabTap’s authorize request).
Paste a SumUp API key (Dashboard → For Developers → Toolkit → API Keys) and merchant code. The key is stored on the server only and is used to verify Tap to Pay charges.
Public app identity. Register bundle ID com.thesocialcode.tabtap on this key.
You have read-only access to SumUp settings.
Stripe
Choose which Stripe API each caller uses for Tap to Pay. Production Cloud Functions read these settings when creating connection tokens and payment intents.
Devices not running in local/debug mode.
iOS app in local mode (sends env=local).
Publishable keys (pk_test_ / pk_live_) are required for emailed payment links. They are safe to store here — they are designed to be public.
You have read-only access to Stripe settings.
Other payment options
Choose which payment methods staff can record from the order screen. Turn cash on or off, and add named options for external card terminals. Extra options are stored as card payments, tagged with the name you enter.
You have read-only access to payment options.