Can each payment partner keep its own document requirements?

Short answer

Yes. Each partner reviews the shared file against its own document requirements, on its own review track, and asks its questions on the exact question or document concerned. The operator decides what each partner sees and whether the merchant sees that partner's name, so partners keep their rules without receiving a separate copy of the file.

In detail

Yes. Each partner reviews the shared file against its own document requirements, on its own review track, and asks its questions on the exact question or document concerned. The operator decides what each partner sees and whether the merchant sees that partner's name, so partners keep their rules without receiving a separate copy of the file.

One file, several readers

Acquirers and payment partners differ in what they need: one wants three months of statements, another a processing history, a third a signed form of its own. A shared onboarding file does not flatten those differences. It stores every document once and lets each partner check the file against its own list.

How it works

  • Each partner has a review track with its own required documents and questions.
  • The operator decides which sections of the file each partner can see.
  • Partners ask questions on the specific question or document, and the merchant answers in place.
  • The operator can hide a partner's identity from the merchant, who then sees a neutral label.

Why this matters

Partners keep their rules and their independence, which they need for their own compliance. The merchant stops receiving three versions of the same request. The operator stops forwarding attachments and loses nothing in control: every share, question and answer is logged with its author and time. Adding a new acquiring partner means adding a track, not redesigning the application.

Still have a question?

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

Book a demo