Paysafe

Payment processing for iGaming with card payments, alternative methods, and payouts.

Detail	Value
Category	iGaming
Base URL	https://api.paysafe.com/paymenthub/v1
Authentication	Bearer Token
Endpoints	5
Connector key	paysafe

Using Paysafe in a workflow

1. Go to Connections and click New Connection.
2. Pick Paysafe 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 /cardpayments/v1/accounts/{accountId}/auths	Authorize a card payment
POST /cardpayments/v1/accounts/{accountId}/auths/{authId}/settlements	Settle an authorization
POST /cardpayments/v1/accounts/{accountId}/settlements/{settlementId}/refunds	Refund a settlement
GET /cardpayments/v1/accounts/{accountId}/auths/{authId}	Get authorization details
POST /cardpayments/v1/accounts/{accountId}/auths/{authId}/voidauths	Void an authorization

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

POST /cardpayments/v1/accounts/{accountId}/auths

Authorize a card payment

Detail	Value
Operation ID	igaming.authorizePayment
Method	POST
Path	/cardpayments/v1/accounts/{accountId}/auths

Parameters

Name	Location	Type	Required
accountId	path	string	Yes

Request Body

Field	Type
merchantRefNum	string
amount	integer
card	object
billingDetails	object

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Paysafe connection from the Connection dropdown.
3. In the Operation dropdown, select igaming.authorizePayment.
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 Paysafe API reference.

POST /cardpayments/v1/accounts/{accountId}/auths/{authId}/settlements

Settle an authorization

Detail	Value
Operation ID	igaming.settlePayment
Method	POST
Path	/cardpayments/v1/accounts/{accountId}/auths/{authId}/settlements

Parameters

Name	Location	Type	Required
accountId	path	string	Yes
authId	path	string	Yes

Request Body

Field	Type
merchantRefNum	string
amount	integer

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Paysafe connection from the Connection dropdown.
3. In the Operation dropdown, select igaming.settlePayment.
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 Paysafe API reference.

POST /cardpayments/v1/accounts/{accountId}/settlements/{settlementId}/refunds

Refund a settlement

Detail	Value
Operation ID	igaming.refundPayment
Method	POST
Path	/cardpayments/v1/accounts/{accountId}/settlements/{settlementId}/refunds

Parameters

Name	Location	Type	Required
accountId	path	string	Yes
settlementId	path	string	Yes

Request Body

Field	Type
merchantRefNum	string
amount	integer

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Paysafe connection from the Connection dropdown.
3. In the Operation dropdown, select igaming.refundPayment.
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 Paysafe API reference.

GET /cardpayments/v1/accounts/{accountId}/auths/{authId}

Get authorization details

Detail	Value
Operation ID	igaming.getAuthorization
Method	GET
Path	/cardpayments/v1/accounts/{accountId}/auths/{authId}

Parameters

Name	Location	Type	Required
accountId	path	string	Yes
authId	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Paysafe connection from the Connection dropdown.
3. In the Operation dropdown, select igaming.getAuthorization.
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 Paysafe API reference.

POST /cardpayments/v1/accounts/{accountId}/auths/{authId}/voidauths

Void an authorization

Detail	Value
Operation ID	igaming.voidAuthorization
Method	POST
Path	/cardpayments/v1/accounts/{accountId}/auths/{authId}/voidauths

Parameters

Name	Location	Type	Required
accountId	path	string	Yes
authId	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Paysafe connection from the Connection dropdown.
3. In the Operation dropdown, select igaming.voidAuthorization.
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 Paysafe API reference.