Compliance

This section is Inflow's compliance policy for Connect (sub-merchants) and virtual IBAN. It is not legal advice, and it does not replace your contract.

The merchant or platform agreement you signed with Inflow, plus any addenda for Connect or virtual IBAN, are what bind you. If anything on this site conflicts with your contract, the contract wins.

Keep in mind:

Passing identity or business verification in the product is not a guarantee that every Inflow feature is available to that account. We can decline, restrict, or pause an account based on our risk and compliance review.
Country and industry lists are maintained by Inflow and change over time. Material updates are communicated through your usual Inflow channel (contract addendum, email, or dashboard notice).
For an authoritative answer on a specific platform, sub-merchant, or feature, ask [email protected].

How rules layer

Eligibility is evaluated at the layers below. The most restrictive relevant layer wins.

Layer	What we check
Sanctions and contract	OFAC sanctions and your Inflow agreement. Applies to every Inflow product, including Connect for cards. See Merchant of Record eligibility for the baseline statement.
Connect business verification	KYC / KYB for sub-merchants, plus the business activities rules: industry disclosure and prohibited sectors.
Virtual IBAN	Additional country and territory restrictions that apply only when Inflow issues a virtual IBAN to a sub-merchant.

A sub-merchant can clear Connect verification and still be ineligible for virtual IBAN. Do not promise a virtual IBAN in your product UX until Inflow confirms availability for that account.

In this section

Business activities: what to disclose and what is prohibited on Connect.
Countries and virtual IBAN: country restrictions and the pre-flight checklist for virtual IBAN.

For the standard merchant baseline (no Connect, or Connect for card payments only): Merchant of Record eligibility.

Support

For eligibility, policy, and feature availability: [email protected].