Banking Circle: institutional accounts, payments, FX and clearing access

Banking Circle provides accounts, payment execution and FX for financial institutions and other accepted businesses. Broker and payment-platform uses include collecting funds, treasury transfers, reconciliation and beneficiary payments. Agency and correspondent banking add clearing access through the bank while preserving client identifiers in the payment chain.[1][4][5]

A virtual IBAN does not by itself establish a direct banking relationship between Banking Circle and the end customer. Its complaints policy explains that payment-provider clients assign virtual accounts to their customers and hold those customers’ account balances. Banking Circle processes the payment after the client or sending bank authorises it. That distinction affects reconciliation, customer communications and where a payment query should begin.[16]

Treasury products add different functions. FlexLiquidity uses rules to physically pool cash across accounts, currencies and entities. The separate deposits proposition describes fiduciary accounts in EUR, GBP and USD, with interest depending on the currency and access during business hours. Neither description supplies a universal yield or the complete terms for an institution’s chosen arrangement.[7][6]

Money Market Funds provide another route for surplus cash. Banking Circle advertises a share class offered with BlackRock, CNAV and LVNAV choices, portal activation and automated sweeping. Availability is expressly limited to existing clients classified as MiFID II Professional Clients or Eligible Counterparties. Fund holdings carry market, credit, interest-rate and liquidity risks; the product page does not promise returns or protection from loss.[8]

The public API overview describes REST requests, JSON responses, OAuth 2 authentication and webhook notifications for payments and other events. Banking Circle says its team supports implementation. The developer guides reached during research required a password, so public evidence establishes these interface features but does not settle endpoint permissions, idempotency behaviour, retry windows or production limits. Those specifications belong in the agreed technical implementation.[9]

The browser-based Client Portal can handle recurring payments, beneficiaries, single and bulk transactions, reports, payment tracking and liquidity management. It supports multiple users with different functions and approval flows. This offers a manual operating channel alongside integration, including a way to define how payment preparation and approval are separated. Accounts documentation also lists SFTP and Swift as delivery routes.[10][1]

For an operating design, distinguish the event notification, the account entry and the downstream scheme result. The portal’s payment tracking and downloadable reports support reconciliation, while the published cutoff rules make clear that an accepted instruction can still be delayed by funding or compliance checks. A notification should therefore be mapped to the documented transaction state used by the institution’s ledger.[10][26]

Banking Circle’s public pages lead to a sales discussion rather than a generally applicable numeric tariff. The reviewed terms place charges in the Pricing Agreement, transaction platform or later notice. Fees are normally billed monthly, exclude taxes unless stated otherwise, and are debited from a Fee Account that must hold at least the agreed monthly minimum.[12]

A payment quote should be evaluated for the route actually used: an internal transfer, a local scheme payment and a correspondent payment are different services. Likewise, the FX value date is a separate input from the payment’s beneficiary delivery time. The public product descriptions establish those distinctions without providing a universal combined price.[2][3][5]

For UK/EEA non-bank payment service providers, onboarding starts with the Initial Client Questionnaire. Applicants must be authorised where active or show that an authorisation application is in its final stages. Banking Circle assesses owners and source of wealth, management, business model, client base, flows, geography, capital and financial-crime controls. A safeguarding account also requires the bank’s safeguarding letter. These criteria are more substantive than completing an API connection.[11]

The same published UK/EEA PSP criteria say that the UK licence restriction excludes applicants classified as micro-enterprises: fewer than ten employees and annual turnover and/or balance-sheet total no greater than EUR 2 million. This is a specific eligibility boundary for that offering, not a test that every applicant in every regional business should assume applies identically.[11]

Project Acacia also records Banking Circle Australia among the collaborators in Canvas’s tokenised government-bond and private-credit-fund pilots. This is useful evidence of a specific settlement-infrastructure role in completed research. It does not establish a generally available CBDC product or a standing permission for all clients to issue or trade tokenised assets through Banking Circle.[14]

The public contact page lists Customer Services hours as Monday to Friday, 08:00–17:30 GMT. The Help Centre groups guidance by payments and FX, accounts and virtual accounts, reporting, administration and API/webhooks. The separate status site breaks incidents into payments, accounts and balances, reporting, notifications and portal login. Its status history is an operational information channel; it does not itself define the client’s service-level agreement.[15][17][18]

Complaints can be raised with the relationship manager or through the contact form. The published policy sets a general one-calendar-month response objective and a 15-business-day payment-services response period, with an exceptional extension to no more than 35 business days. It also gives an authorised-manager escalation route and explains when a complainant may approach the CSSF.[16]

The core operator is Banking Circle S.A., Luxembourg register B222.310, with LEI 213800W1NGBLERUS6M39. The ECB’s supervised-entities list with a 1 July 2026 cut-off identifies that exact entity and LEI as a credit institution in Luxembourg’s less-significant-entity list. Banking Circle’s current regulatory directory identifies the CSSF as its home regulator and gives registration LUB00000408. The bank’s authorisation is distinct from each client’s permission to conduct its own business.[20][19]

The Risk Appetite Policy excludes direct consumer service, physical cash pay-ins/pay-outs, binary options and unregulated investment firms managing or investing third-party funds. CFD and investment-firm business in correspondent banking is restricted: relevant licences, jurisdictions and enhanced diligence matter, including evidence of suitability and appropriateness testing. Crypto-asset providers have additional authorisation and control requirements. A broker’s regulated status alone therefore does not establish acceptance of its business model, customers or payment flows.[21]

The March 2025 terms say that the bank belongs to the FGDL, but deposits of credit institutions and other regulated financial institutions are ineligible under the stated terms. Safeguarding needs separate acknowledgement terms. The document also says funds ultimately held with the Luxembourg bank are outside UK FSCS protection.[12]

The FGDL’s own explanation distinguishes financial institutions’ own-account deposits from eligible customers’ money in an omnibus account. For beneficial-owner treatment, the bank must have the relevant third-party identification and entitlement information; limits are per eligible depositor per bank. Accordingly, a virtual IBAN, safeguarding label or group banking licence is insufficient to establish protection for a particular balance.[22]

Banking Circle’s current company page dates the acquisition by EQT VIII and EQT Ventures, together with its founders, to September 2018. EQT still lists Banking Circle in its current portfolio. The earlier transaction announcement used the name Saxo Payments Banking Circle and described the acquisition from Saxo. This history explains the legacy alias; the present Banking Circle profile is a separate provider record from Saxo Institutional.[23][24][25]

Operator

Banking Circle S.A.

Service scope

Business-to-business accounts, payment execution, agency and correspondent banking, FX and treasury services for accepted institutional clients.

Customer types

Banks; Payment institutions; Electronic money institutions; Acquirers; Account and payment platforms; Eligible investment and CFD firms subject to enhanced diligence

Delivery

API; Hosted

Pricing publication

Quote only

Headquarters

Luxembourg

Platforms

Banking Circle API; Banking Circle Client Portal; BC-NOW; FlexLiquidity

Integrations

REST API; OAuth 2; Webhooks; Client Portal; SFTP; Swift

Pricing scope

Bespoke Pricing Agreement; FX margins and minimum fees depend on the agreed service and activity.

Implementation

Business and financial-crime onboarding precedes agreed account setup, channel integration and operational approval/reconciliation design.

Support

Customer Services, relationship-manager contacts, Help Centre, service-status site and a published complaints process.

Permissions and regulatory scope

Luxembourg credit institution independently matched to the ECB list. Regional subsidiaries and branches have separate serving-entity considerations; client acceptance and deposit eligibility require the specific account and business scope.

Provider metadata checked 20 Oct 2026Source 19Source 20Source 1Source 2Source 4Source 5Source 3Source 7Source 9Source 10Source 11Source 21Source 15Source 17Source 18Source 12Source 25

The cutoff page conditions same-day processing on successful initiation, sufficient funds and compliance/internal-policy checks. For a payment involving conversion, forwarding to the correspondent bank follows FX settlement. These dependencies should sit alongside the institution’s treasury funding schedule and payment-routing rules.[26]

The March 2025 terms call for immediate reporting of transaction errors and generally impose a 30-day written-objection limit. Either party can terminate for convenience with three months’ written notice; specified breach or risk events permit earlier termination. Ending the relationship leaves outstanding transactions and charges to be settled. These published terms should be reconciled with any individually agreed provisions.[12]

The operating choice is therefore concrete: select the account structure, clearing route and channel that match the institution’s flows, then document approvals, reconciliation and customer-query ownership around them. Agency access, virtual-account collections and treasury investments each introduce different participants and records; the contract and integration should describe the selected combination.[4][1][10][8]