Does a merchant fill in its KYB again for each payment partner?

Short answer

The merchant completes one KYB. From it you generate one application per payment partner, each carrying the subset of information you chose to share. Submitting to a second partner creates a second application, and the merchant starts nothing over.

In detail

No. The merchant record and the application are two separate objects, and that separation is what keeps the merchant from starting over. The merchant answers your KYB once. Each application is generated from that record, attached to a single payment partner, and carries only the subset of the file you decide to share with that partner.

When a profile needs a second or third partner, you create a new application from the same record. It runs its own lifecycle, from Sent through due diligence to Live, with its own status and its own review history, while the other applications move at their own pace. The merchant goes Active as soon as one application does, and moves into your payment stack.

What this changes for your team

  • Your analysts maintain one merchant file instead of one copy per partner.
  • Each partner receives the sections it needs, such as the ownership structure, and nothing more.
  • Every share carries a sender, a recipient and a timestamp, so you can account for each transfer.

For the merchant, the experience stays simple: one questionnaire, one place to answer follow-up questions, and a status to follow. For you, it means a merchant can be presented to several payment partners in parallel without any duplicated data entry, and the information each partner sees stays under your control.

Still have a question?

Our team walks you through the platform with your use case on the table.

Book a demo