One provider’s “Approved” isn’t another’s

At Bennu, I recently saw two different misunderstandings interrupt a workflow. In one review, a question came up about whether a document was complete, although the full file was already in our records. Elsewhere, an instruction about company ownership and control looked like a request to deposit money. We answered the first from the file already held in Bennu; the review team confirmed the document, and the member did not have to send it again. In the second case, we explained that no deposit was due and checked Sumsub and MoonPay Enterprise separately before continuing.

That distinction matters to me as a co-founder: “Approved” in Sumsub does not mean “Approved” by MoonPay Enterprise. They are separate decisions, and the product should make clear what we have, what was reviewed and which provider still has a decision to make.

A verification answers a specific question

A KYC or KYB process collects and reviews information about a person or company. Depending on the flow, that may include identity, documents, ownership structure and representatives. Sumsub’s public documentation describes that work and makes clear that the company configuring the process decides what data and conditions it needs. In practice, it also matters that a provider reads the file as a whole: if information already held in Bennu is interpreted differently, it is our job to clarify it first.

That is why “identity verified” and “virtual account approved” are not interchangeable. A verification result may be one input to a later process. The entity offering the service keeps its own requirements and may ask for more information, accept the file or decline the application. None of those decisions should be hidden behind a green check that does not explain what was checked.

We should also be precise with the word “reuse”. The fact that a platform can share verification data does not mean every provider will accept it, that it will be reused automatically, or that the person will have no further steps. The recipient, purpose and applicable notice or authorization need to be clear.

A quote is not a completed transaction

The second distinction appears when buying or selling digital assets. Before confirmation, a quote can answer practical questions: how much money is being paid, which asset is expected, what costs are shown and which payment method is selected. MoonPay publishes supported payment methods and regional availability; that list shows why an option depends on location and may change.

But a quote is an offer for specific conditions. It does not prove that a card or bank transfer was accepted, that the provider completed its checks, that a conversion finished or that a network confirmed delivery. Each stage has a different status. A good screen should name the status we know and avoid announcing the next one prematurely.

As a product designer, I try to follow one rule: show the amount and charges available before asking for confirmation, then communicate the result that actually comes back. If a response is still being reconciled, “under review” or “checking” is more honest than “complete”. Availability, limits and outcomes depend on the provider’s terms and checks and on the route selected.

Same group does not mean same product

Another distinction matters when services share a corporate name. MoonPay Ramps is an integration for buying or selling digital assets with fiat payment methods. MoonPay Enterprise is a different service line for business payment infrastructure and eligible virtual accounts. A shared corporate name does not make those integrations the same product, and a verification or status in one route does not approve the other.

At Bennu we explain which MoonPay service is involved in each flow, with availability, eligibility and conditions depending on service and country. I see that as basic clarity: people should be able to tell which service they are using and which terms apply, without having to infer it from a logo or a familiar brand.

Language that does not claim more than it knows

For a fintech team, the practical lesson is to keep evidence, provider decisions and account eligibility distinct. Check the file already held, resolve interpretation with the provider, and show which decision is still outstanding. That gives operations a clearer next step and avoids asking a member to repeat information already on file.

Bennu is designed for eligible companies collecting internationally through EUR/SEPA and USD/SWIFT accounts in the company’s name, with settlement to self-custody. Third-party deposits and rail access depend on the account, corridor and provider review. If that matches your workflow, you can request access. A request is not an approval or a guarantee of availability.

I am writing from my work as a co-founder of Bennu. Sumsub and MoonPay are mentioned as providers and public sources; neither sponsors nor endorses this article. It is informational and is not legal, regulatory or financial advice.

Sources

• Sumsub: What is Business Verification.
• Sumsub: How Business Verification works.
• MoonPay: Supported payment methods.
• MoonPay: Terms of Use and services.