Skip to main content
Payment settings control which supported checkout methods your shop offers in Tapp. The Management Admin App currently exposes Tap to Pay on iPhone, Tap to Pay on Android, and cash as Owner-managed switches.

​
Who can do this?

Owners can use this workflow with the scope described here. Write access is checked for the currently selected shop. Backend authorization is authoritative; entering a route directly does not expand a role.

​
Where

Select Settings for the correct shop and use the Payments section on the main Settings page.

​
Steps

  1. Review the current switch for each displayed payment method.
  2. Toggle only the methods the shop can operationally support.
  3. When enabling Tap to Pay on iPhone without recorded consent, read the required information dialog before continuing.
  4. Select Save changes after the form becomes dirty and wait for saving to finish.
  5. Test the intended method in the appropriate checkout flow before relying on it.

​
Platform notes

The web form writes the complete payment-settings object. SEPA, Klarna, PayPal, and Girocard fields exist in the data model but are intentionally hidden and fixed by the Admin App; they are not merchant-configurable controls and are not documented as such. Device-level capability and user-level Tap to Pay setup can still determine whether an enabled method is usable on a specific device.

​
Market notes

The displayed core switches exist for GB and DE. Availability is not a promise that every method works on every device or account. Do not infer DE-only methods from hidden backend fields; only use controls actually shown in the current Admin App.

​
Troubleshooting

If saving fails, keep the page open, confirm the shop and Owner role, and retry after reloading current values. If a saved method is missing at checkout, check shop-level enablement, the user’s device capability, and the relevant platform permission rather than repeatedly toggling the setting.