Connect Paystand API operations to a Flowgear Workflow through template-driven query, create, update, and action methods.
0.0.0.1 - Initial release.
Use this Connection to store the Paystand credentials and runtime settings shared by all methods.
| Property |
Type |
Description |
Base Url |
String |
Base URL for Paystand API calls. Leave the default unless Paystand gives you a different host. |
Client Id |
String |
Client identifier used to request bearer tokens for authenticated endpoints. |
Client Secret |
Masked |
Client secret used to request bearer tokens for authenticated endpoints. |
Customer Id |
String |
Customer identifier sent in the X-CUSTOMER-ID header for authenticated endpoints. |
Publishable Key |
Masked |
Publishable key sent in the X-PUBLISHABLE-KEY header for public endpoints. |
Scope |
String |
OAuth scope requested during token acquisition. Leave the default auth unless Paystand instructs you otherwise. |
Timeout (seconds) |
Integer |
Request timeout used for connection validation and runtime API calls. |
- Request Paystand Developer API access from Paystand and collect the
clientId, clientSecret, customerId, and publishableKey values for your application.
- Create the Flowgear Connection and leave
Base Url as https://api.paystand.co/v3 unless Paystand gives you an environment-specific host.
- Enter
Client Id, Client Secret, and Customer Id when you will call authenticated operations such as balances, banks, payments, refunds, transfers, withdrawals, disputes, and payer resources.
- Enter
Publishable Key when you will call public Assurety operations that use X-PUBLISHABLE-KEY.
- Leave
Scope as auth unless Paystand instructs you to request a different scope.
- Run the Connection test before you build a Workflow. The test validates token acquisition and a low-risk balance-summary call.
The Node exposes metadata-driven methods so you can select a supported Paystand OperationId from templates instead of building raw HTTP requests.
Use Query for supported GET operations such as balances, payments, disputes, transfers, withdrawals, customer resources, and Assurety lookups.
| Parameter |
Type |
Description |
Connection |
Connection |
Paystand Connection details. |
OperationId |
String |
Template-selected identifier for the Paystand read operation to execute. |
Options |
Object |
Path and query values required by the selected operation. |
| Return |
Type |
Description |
Response |
Array |
One response row per returned item or singleton result, preserving provider fields under Response and the normalized Flowgear status under Response.Flowgear. |
Use Create for supported resource-creating POST operations such as payments, refunds, withdrawals, banks, payers, scheduled payments, and Assurety resources.
| Parameter |
Type |
Description |
Connection |
Connection |
Paystand Connection details. |
OperationId |
String |
Template-selected identifier for the Paystand create operation to execute. |
Options |
Object |
Path and query values required by the selected operation. |
Items |
Array |
JSON request body rows for the selected operation. |
| Return |
Type |
Description |
Response |
Array |
One response row per submitted item, including the provider payload and Response.Flowgear success or failure details. |
Use Update for supported PUT operations such as resource updates, bank verification, and settings changes.
| Parameter |
Type |
Description |
Connection |
Connection |
Paystand Connection details. |
OperationId |
String |
Template-selected identifier for the Paystand update operation to execute. |
Options |
Object |
Path and query values required by the selected operation. |
Items |
Array |
JSON request body rows for the selected operation. |
| Return |
Type |
Description |
Response |
Array |
One response row per submitted item, including the provider payload and Response.Flowgear success or failure details. |
Use Action for supported non-create POST operations such as activate, deactivate, disclose, request history, drop amounts, set default bank, stop schedules, and resume schedules.
| Parameter |
Type |
Description |
Connection |
Connection |
Paystand Connection details. |
OperationId |
String |
Template-selected identifier for the Paystand action operation to execute. |
Options |
Object |
Path and query values required by the selected operation. |
Items |
Array |
Optional JSON request body rows for the selected action. |
| Return |
Type |
Description |
Response |
Array |
One response row per submitted action item, including the provider payload and Response.Flowgear success or failure details. |
- Use the template picker to choose the
OperationId that matches the Paystand endpoint you want to call. Templates provide the expected Options and Items structure for that operation.
- The Node chooses the required auth mode from operation metadata. Authenticated operations use bearer auth plus
X-CUSTOMER-ID, while public operations use X-PUBLISHABLE-KEY.
- Query methods flatten Paystand
results envelopes into one row per item. Empty list responses return zero rows instead of a synthetic success row.
GET /balances/summary is flattened into one row per Currency and AccountKey, and the original balance object is preserved under Response.PaystandRawBalance.- The Node handles supported Paystand
limit and offset paging internally, so you do not need to manage transport paging in the Workflow for standard list operations.
- When Paystand returns a raw
401 Unauthorized, the Node acquires a fresh bearer token and retries the request once before surfacing the failure.
- Paystand's published docs reviewed for this connector do not clearly identify a separate sandbox host. If Paystand gives you a sandbox-specific host, update
Base Url manually before testing.