Nuvei

iGaming payment processing with deposits, withdrawals, and KYC verification.

Detail	Value
Category	iGaming
Base URL	https://ppp-test.nuvei.com/ppp/api/v1
Authentication	HMAC-SHA256
Endpoints	6
Connector key	nuvei

Using Nuvei in a workflow

1. Go to Connections and click New Connection.
2. Pick Nuvei from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
POST /openOrder	Open an order (session)
POST /payment	Process a payment
POST /payout	Process a withdrawal/payout
POST /getPaymentStatus	Get payment status
POST /voidTransaction	Void a transaction
POST /refundTransaction	Refund a transaction

Each endpoint is documented in full below. Use the outline on the right to jump to one.

POST /openOrder

Open an order (session)

Detail	Value
Operation ID	igaming.openOrder
Method	POST
Path	/openOrder

Parameters

No parameters.

Request Body

Field	Type
merchantId	string
merchantSiteId	string
clientRequestId	string
currency	string
amount	string

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Nuvei connection from the Connection dropdown.
3. In the Operation dropdown, select igaming.openOrder.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Nuvei API reference.

POST /payment

Process a payment

Detail	Value
Operation ID	igaming.createPayment
Method	POST
Path	/payment

Parameters

No parameters.

Request Body

Field	Type
sessionToken	string
merchantId	string
currency	string
amount	string
paymentOption	object

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Nuvei connection from the Connection dropdown.
3. In the Operation dropdown, select igaming.createPayment.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Nuvei API reference.

POST /payout

Process a withdrawal/payout

Detail	Value
Operation ID	igaming.createPayout
Method	POST
Path	/payout

Parameters

No parameters.

Request Body

Field	Type
merchantId	string
userTokenId	string
amount	string
currency	string

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Nuvei connection from the Connection dropdown.
3. In the Operation dropdown, select igaming.createPayout.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Nuvei API reference.

POST /getPaymentStatus

Get payment status

Detail	Value
Operation ID	igaming.getPaymentStatus
Method	POST
Path	/getPaymentStatus

Parameters

No parameters.

Request Body

Field	Type
sessionToken	string

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Nuvei connection from the Connection dropdown.
3. In the Operation dropdown, select igaming.getPaymentStatus.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Nuvei API reference.

POST /voidTransaction

Void a transaction

Detail	Value
Operation ID	igaming.voidTransaction
Method	POST
Path	/voidTransaction

Parameters

No parameters.

Request Body

Field	Type
merchantId	string
relatedTransactionId	string
amount	string
currency	string

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Nuvei connection from the Connection dropdown.
3. In the Operation dropdown, select igaming.voidTransaction.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Nuvei API reference.

POST /refundTransaction

Refund a transaction

Detail	Value
Operation ID	igaming.refundTransaction
Method	POST
Path	/refundTransaction

Parameters

No parameters.

Request Body

Field	Type
merchantId	string
relatedTransactionId	string
amount	string
currency	string

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Nuvei connection from the Connection dropdown.
3. In the Operation dropdown, select igaming.refundTransaction.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Nuvei API reference.