← Practical guides

Compare providers by funds flow

Compare treasury, customer-payment and embedded-ramp research scenarios using dated evidence and explicit acceptance gaps.

FiatBridge · Updated

Editorial preparation guidance, not financial or legal advice. Requirements depend on your entity, activity and jurisdiction. Sources are linked within each guide.

Choose the funds flow before comparing providers. These are generic research scenarios, not a recommendation for a particular company. All linked listings remain pending. Sources were reviewed on 7 November 2026; next review is due by 5 February 2027.

Company treasury: your own money

Example: a company pays suppliers and manages its own fiat and digital assets without collecting money for customers.

Ask which entity contracts with you, whether your activity and countries are accepted, and whether the account supports each intended counterparty. Obtain the complete fee schedule, minimum commitment and expected onboarding steps. Insufficient data is available here for a cost or onboarding-speed ranking.

Customer collections and payouts: other people’s money

Example: an exchange wants customers to pay in and withdraw fiat. This requires an explicit account-ownership and funds-flow agreement.

Ask for written confirmation of who owns each account, who receives each payment, who safeguards or holds funds, which entity owes money to the customer, and who performs customer checks. Compare returned payments, reconciliation, disputes, reserves and exit arrangements on the same flow.

Embedded crypto purchase or sale

Example: a wallet integrates a provider’s purchase/sale flow for its users. Partner approval and end-user eligibility are separate checks.

Ask who contracts with the end user, which countries and payment methods are supported for each direction, who handles refunds and support, and what remains your responsibility. Obtain production approval separately from sandbox credentials.

Embedded accounts and cards

Solaris documents a business-customer identification flow for platform integrations. Railsr publishes a restriction on onboarding new agents/distributors without prior written FCA consent. Confirm partner admission and the current regulatory position before budgeting an implementation.

Compare only like-for-like offers

Use the KYB preparation checklist and record the applicant country, activity, own/customer funds, currencies, counterparties and monthly volume. Request a dated proposal for that same brief from each candidate. Keep unsupported fields as “Not confirmed”; a missing price is not a zero price.

The provider profiles link each statement to its primary source and explain its limits. No candidate on this page has been approved for your scenario, and no winner is inferred from incomplete data.

Explore providers →
Prepare your requirements