Appearance
Trustly
Open banking payments for iGaming with deposits, withdrawals, and direct debits via JSON-RPC.
| Detail | Value |
|---|---|
| Category | iGaming |
| Base URL | https://api.trustly.com/1 |
| Authentication | HMAC-SHA256 |
| Endpoints | 9 |
| Connector key | trustly |
Using Trustly in a workflow
- Go to Connections and click New Connection.
- Pick Trustly from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
POST / | Initiate deposit |
POST / | Player withdrawal |
POST / | Refund deposit |
POST / | Player bank selection |
POST / | Direct debit charge |
POST / | API-only payout |
POST / | List withdrawals |
POST / | Approve withdrawal |
POST / | Deny withdrawal |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
POST /
Initiate deposit
| Detail | Value |
|---|---|
| Operation ID | igaming.deposit |
| Method | POST |
| Path | / |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
method | string |
params | object |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Trustly connection from the Connection dropdown.
- In the Operation dropdown, select
igaming.deposit. - 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 Trustly API reference.
POST /
Player withdrawal
| Detail | Value |
|---|---|
| Operation ID | igaming.withdraw |
| Method | POST |
| Path | / |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
method | string |
params | object |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Trustly connection from the Connection dropdown.
- In the Operation dropdown, select
igaming.withdraw. - 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 Trustly API reference.
POST /
Refund deposit
| Detail | Value |
|---|---|
| Operation ID | igaming.refund |
| Method | POST |
| Path | / |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
method | string |
params | object |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Trustly connection from the Connection dropdown.
- In the Operation dropdown, select
igaming.refund. - 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 Trustly API reference.
POST /
Player bank selection
| Detail | Value |
|---|---|
| Operation ID | igaming.selectAccount |
| Method | POST |
| Path | / |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
method | string |
params | object |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Trustly connection from the Connection dropdown.
- In the Operation dropdown, select
igaming.selectAccount. - 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 Trustly API reference.
POST /
Direct debit charge
| Detail | Value |
|---|---|
| Operation ID | igaming.charge |
| Method | POST |
| Path | / |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
method | string |
params | object |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Trustly connection from the Connection dropdown.
- In the Operation dropdown, select
igaming.charge. - 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 Trustly API reference.
POST /
API-only payout
| Detail | Value |
|---|---|
| Operation ID | igaming.accountPayout |
| Method | POST |
| Path | / |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
method | string |
params | object |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Trustly connection from the Connection dropdown.
- In the Operation dropdown, select
igaming.accountPayout. - 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 Trustly API reference.
POST /
List withdrawals
| Detail | Value |
|---|---|
| Operation ID | igaming.getWithdrawals |
| Method | POST |
| Path | / |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
method | string |
params | object |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Trustly connection from the Connection dropdown.
- In the Operation dropdown, select
igaming.getWithdrawals. - 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 Trustly API reference.
POST /
Approve withdrawal
| Detail | Value |
|---|---|
| Operation ID | igaming.approveWithdrawal |
| Method | POST |
| Path | / |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
method | string |
params | object |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Trustly connection from the Connection dropdown.
- In the Operation dropdown, select
igaming.approveWithdrawal. - 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 Trustly API reference.
POST /
Deny withdrawal
| Detail | Value |
|---|---|
| Operation ID | igaming.denyWithdrawal |
| Method | POST |
| Path | / |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
method | string |
params | object |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Trustly connection from the Connection dropdown.
- In the Operation dropdown, select
igaming.denyWithdrawal. - 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 Trustly API reference.