TAP TAP GO
Draw the commercial relationships
Identify who sells to the buyer, who receives the payment and who owes the seller money. Show platform charges, refunds and disputed orders separately. Present that map to prospective providers and qualified advisers rather than describing the business simply as an online marketplace. Similar-looking websites can have different payment arrangements, and the financial service must fit the actual roles and responsibilities of the parties involved in each transaction.
Evaluate records and exceptions together
Ask how each order connects to incoming payments, fees and any seller payout. Request examples of a cancellation, partial refund and withheld or reviewed movement under the proposed programme. Keep seller communication and support ownership in the evaluation. A smooth buyer checkout is valuable, but the platform also needs a defensible operational record showing what happened after the purchase and which party is responsible when the order or payment does not follow the normal path.
Hypothetical example
A hypothetical specialist marketplace initially plans to receive all payments into a general account. After mapping seller obligations and refunds, the founders discuss the model with suitable providers and advisers. The exercise shapes the payment architecture before a convenient but potentially unsuitable account becomes central to operations.
Make it practical.
Use this checklist as you read. Checks are not stored.References & further reading
Background reading — EBA: findings on virtual IBAN arrangements ↗Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.
