EUR virtual IBAN to USDC API

Provision a dedicated EUR virtual IBAN per account, attribute each incoming SEPA payment by its reference code, and convert the received EUR into USDC on a supported chain – through one API, without building custody or FX yourself.

Four steps from SEPA credit to USDC balance

Create or onboard the party – POST /accounts with inline KYC/KYB data. Wallets auto-provision on the account's chain.
Provision a dedicated EUR virtual IBAN – POST /accounts/{accountId}/virtual-bank-accounts with inCurrency "EUR" and targetCryptocurrency "USDC". The response carries iban, bic, bankName, beneficiaryName and referenceCode.
Receive and attribute the SEPA payment – the payer quotes the referenceCode in the remittance field, so attribution does not depend on name matching.
Convert the received EUR into USDC – credited on the account's chain (Base, Avalanche or Polygon) with a full exportable trail.

Good fit

PSPs and payment platforms adding a stablecoin settlement option to an existing EUR payout flow
Marketplaces paying sellers who want USDC instead of a local bank transfer
Fintechs needing per-seller EUR collection accounts with automatic reconciliation

Not a fit

Consumer retail onramps or single-user wallet top-ups
Non-EUR pay-ins into this flow
Card-present acceptance or acquiring

Current limitations

Virtual IBANs issued through this flow are EUR pay-in accounts today.
Timing depends on the SEPA rail, compliance checks and onchain execution – settlement is not guaranteed instant.
Attribution relies on the referenceCode being present in the incoming transfer.

Compliance scope

Every receiving account is KYC/KYB verified before a virtual IBAN is issued. Where a leg is a regulated activity it executes under named licensed partner institutions. Our MiCA authorization is in progress and is not presented as complete. Whether you need your own permissions depends on your role, your flow and your jurisdiction.

Frequently asked

How is an incoming SEPA payment matched to the right account?

By the referenceCode returned when the virtual IBAN is provisioned. The payer quotes it in the transfer reference and the credit is attributed to that account.

Which fields come back when the virtual IBAN is created?

iban, bic, bankName, beneficiaryName and referenceCode, alongside the virtual bank account id.

How fast does the EUR arrive as USDC?

It depends on the SEPA rail used, compliance checks on the incoming payment, and onchain execution. There is no guaranteed instant settlement time.

Which chains and stablecoins are supported?

USDC and EURC on Base, Avalanche and Polygon.

Do we need our own licence?

It depends on your role, flow and jurisdiction. Some platforms hold their own CASP/VASP/MSB permissions and use Venly as a technology provider; others run regulated execution through licensed partner infrastructure.