Skip to main content
KYC status combines verification and provider capability signals with Tapp’s due-diligence state. These fields answer different questions and must not be collapsed into a single assumption about account readiness.

​
Who can do this?

Owners and Managers and Staff 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

The Owner sees KYC progress in the Set up your shop flow. The store KYC-status endpoint is authorized for Owner, Manager, and Staff, although current Admin navigation does not provide Managers or Staff a dedicated KYC status page.

​
Steps

  1. verified indicates whether the API’s required capability checks are valid and allowed.
  2. canReceivePayments reflects the receivePayments capability.
  3. canSendToTransferInstrument reflects the payout/transfer-instrument capability.
  4. Due diligence is separately pending, approved, or rejected. Tapp treats approved as the completed call/review step.
  5. dueDiligenceCallBookedAt records that the booking webhook supplied a booking timestamp; it is not the same as due-diligence approval.
  6. Re-read status after completing KYC or booking the call rather than inferring success from a redirect.

​
Platform notes

The Admin query reduces the raw capability records to the values used by setup. The Owner-only setup pill fetches this status and reacts to verified, due-diligence state, and call booking. Backend read authorization is broader than that UI exposure. Payment services separately block payment acceptance while due diligence is pending or rejected.

​
Market notes

Status field semantics are shared by GB and DE. Provider requirements and the route to obtaining valid capabilities can vary, so do not promise approval, payout readiness, or a reason based only on market or language.

​
Evidenced troubleshooting

Missing legal entity or account-holder data can prevent a status response. Provider retrieval errors and rate limiting can also occur. If fields appear contradictory, capture the entire displayed state, selected shop, role, and time for @sebestil. Do not interpret a rejected state’s cause unless the product explicitly supplies one.