PAYMENTS

Keep payment credentials with the provider. Keep financial control in Nexus.

Nexus is designed for hosted provider flows, signed webhooks, provider-neutral transaction lifecycles and full reconciliation after external confirmation.

HOSTED PAYMENT FLOW

Connected products do not need to store raw card credentials.

A connected platform creates a Nexus funding intent. Nexus creates the approved provider session and sends the user into a hosted payment experience. Provider confirmation returns through signed server-side events before the ledger is posted.

Connected platformFunding intentPay NexusHosted provider checkoutVisa / Mastercard / approved methodsWebhook confirmationNexus ledger

Funding

Card, bank and alternative-payment rails can fund the account without being embedded into every connected service.

Payout

Approved payout requests move through KYC, risk, limit and provider controls before external value leaves the system.

Fee attribution

B2B Nexus fees can be accrued to the originating or responsible operator while preserving the full approved value for the end user.

OPERATOR ATTRIBUTION

Every external flow belongs to an authenticated operator context.

Operator identity should come from the integration credential, not from an arbitrary client-supplied field. That identity becomes part of the immutable external-flow record.

Inbound example

direction: IN
origin_operator: CASINO_A
rail: CARD
currency: EUR
amount: 100.00
player_value: 100.00
nexus_fee_payer: CASINO_A

Outbound example

direction: OUT
responsible_operator: CASINO_B
rail: BANK_PAYOUT
currency: EUR
amount: 500.00
player_receives: 500.00
nexus_fee_payer: CASINO_B

APPROVED USE ONLY

Payment separation is not payment concealment.

Nexus can separate the user experience and technical integration from a connected iGaming product, but the relevant acquirer, EMI or payment partner must understand and approve the downstream use cases it supports.

Read our compliance approach