How does a payment partner review an application?
Each partner opens the applications you route to it in its own portal, reads what you shared, and asks for anything missing inside the file. The request reaches the merchant, who answers and attaches the document in the same thread.
In detail
You configure your payment partners in your program, and each partner gets its own access. The applications you route to a partner land in its own portal, where its reviewers open them, read the information you chose to share and work the file without leaving the platform.
The partner sees the application and only the application. Your internal risk notes and your pipeline stay in your own view. When a reviewer needs one more document or a clarification, the question is asked from inside the application. It reaches the merchant in its own portal, and the merchant answers in the same thread, attaching a new document or one already stored in its vault.
Everything stays on the record
Every question and answer lands in the merchant's file, tagged and searchable, with one thread per topic. Each message is timestamped, so you can measure response time per merchant, per analyst and per partner against your SLA, and spot where files slow down.
The decision stays with the partner. What you control is how quickly a complete file reaches the team that reviews it, and how clearly each exchange is documented. You follow every application from Sent, through due diligence, to Live, and a merchant becomes Active the moment one of its applications does.