Skip to main content
KYC verification is started from Tapp but completed in a provider-hosted onboarding session. The Owner action requests a fresh hosted URL, so the same control is also used to resume after an unfinished session.

​
Who can do this?

Owners can use the information with the scope described. Only Owners may start or resume KYC. API status read access exists for all three store roles even though the current Admin UI presents progress only to the Owner.

​
Where

In the Management Admin App, open the persistent Set up your shop pill. KYC becomes the active setup step after shop setup and at least one menu category and item are complete. The pill is shown for the Owner.

​
Steps

  1. Confirm the selected shop and that you are its Owner.
  2. Open the setup overview and choose Complete identification for the KYC step.
  3. Wait while Tapp requests a hosted onboarding URL. A valid URL opens in a new browser tab.
  4. Complete only the fields and evidence requested in that hosted session. This article does not prescribe a document list because requirements are not defined by the current Tapp UI and can vary.
  5. If you leave before completion, return to the same KYC action to request a fresh hosted link. Do not rely on an old tab.
  6. Return to Tapp and allow the status query to refresh.

​
Platform notes

The browser never receives provider API credentials; the Tapp API creates the hosted link. Starting requires the Owner role. KYC status is read separately, so opening or closing the hosted page does not itself mark the step complete. The setup sequence uses verified from the status response.

​
Market notes

The same category and Owner workflow cover GB and DE, while the hosted session can present market-appropriate requirements. Do not copy assumptions between markets or treat the interface language as the shop country. KYC information here is product guidance, not legal advice.

​
Evidenced troubleshooting

If no URL opens, allow pop-ups for the deliberate action and retry once. Evidenced API failures include missing business or owner data, inactive business, incomplete shop, non-Owner access, an already active process, unsupported business type or country, rate limiting, and provider/system failure. Preserve the exact message and escalate to @sebestil; do not invent missing requirements.