By IFX Payments

IFX ibanq

IFX multicurrency payment-account infrastructure with named IBANs, subaccounts and API access.

The offering

What IFX ibanq does

ibanq underpins IFX’s business payment accounts and money movement. The current offer describes balances in multiple currencies, named virtual IBANs, subaccounts, team permissions and SWIFT, SEPA and Faster Payments. API access connects account and transaction operations to a client’s systems.

For gambling, agree the eligible jurisdictions and immediate end-client flow under the current addendum. Clients must fund winnings payments and hold the required consents; layered gaming transactions and end-client account access have specific restrictions. Map business and player-related balances carefully. IFX safeguards for its own clients, while an operator’s obligations toward player funds remain a separate responsibility.

Who should explore it?

Eligible gambling operators and related businesses structuring multicurrency operational funds and payments.

  • Manage permitted supplier and operational payments
  • Structure eligible gambling-related fund flows with account reconciliation

Documented capabilities

  • Named virtual IBANs
  • Multicurrency balances and transfers
  • Subaccounts and permissions
  • API-connected account and payment operations

Reported in the linked public sources. We have not independently tested these capabilities.

Product details

Infrastructure role
Multicurrency business payment accounts on IFX’s ibanq infrastructure.Source
Account structure
Named virtual IBANs and subaccounts can separate balances by client, entity or purpose.Source
Payment rails
SWIFT, SEPA and Faster Payments are listed for the account platform.Source
Gambling limits
Permitted end-client jurisdictions are Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Guernsey, Isle of Man, Italy, Jersey, Malta, Netherlands, Poland, Romania, Spain and the United Kingdom. Immediate end-client flows, valid consents and sufficient winnings funding are required; additional restrictions may apply.Source
Responsibility boundary
IFX is an EMI and safeguards on behalf of its clients; clients remain responsible for obligations involving their own customers’ funds.Source
Systems connection
IFX’s API connects ibanq payment, account-management and reconciliation operations.Source

Delivery & commercial details

Delivery & integration
IFX (UK) Ltd payment-account service built on ibanq, with online account operations and API access; gambling use is subject to current contract and addendum.Source
Pricing
Request account, transfer, FX, API and return charges for the approved structure. The reviewed public account page does not establish one numeric gambling tariff.

Confirm market availability, rights, service levels and contractual terms for your implementation. API availability alone does not establish a named integration.

Buyer questions, answered

Can a player use the operator’s ibanq subaccount directly?

The current gambling addendum prohibits end-client access to ibanq or its subaccounts without IFX’s prior written consent.

Source
Can an operator send winnings without funding the account?

The addendum makes IFX’s obligation to pay winnings conditional on sufficient client funds. The client must fund the payment first if the balance is insufficient.

Source
Are all countries eligible for gambling-related transactions?

No. The addendum defines permitted jurisdictions and prohibits transactions involving end clients elsewhere. Review the current permitted list and any additional restrictions with IFX.

Source