POST /v1/treasury/financial_accounts
Creates a new FinancialAccount. Each connected account can have up to three FinancialAccounts by default.
Servers
- https://api.stripe.com/
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/x-www-form-urlencoded" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
platform_restrictions |
Object | No |
The set of functionalities that the platform can restrict on the FinancialAccount. |
platform_restrictions.outbound_flows |
String | No |
Possible values:
|
platform_restrictions.inbound_flows |
String | No |
Possible values:
|
nickname |
No |
The nickname for the FinancialAccount. |
|
expand[] |
Array | No |
Specifies which fields in the response should be expanded. |
metadata |
Object | No |
Set of key-value pairs that you can attach to an object. This can be useful for storing additional information about the object in a structured format. Individual keys can be unset by posting an empty value to them. All keys can be unset by posting an empty value to |
supported_currencies[] |
Array | Yes |
The currencies the FinancialAccount can hold a balance in. |
features |
Object | No |
Encodes whether a FinancialAccount has access to a particular feature. Stripe or the platform can control features via the requested field. |
features.financial_addresses |
Object | No | |
features.financial_addresses.aba |
Object | No | |
features.financial_addresses.aba.requested |
Boolean | Yes | |
features.outbound_payments |
Object | No | |
features.outbound_payments.us_domestic_wire |
Object | No | |
features.outbound_payments.us_domestic_wire.requested |
Boolean | Yes | |
features.outbound_payments.ach |
Object | No | |
features.outbound_payments.ach.requested |
Boolean | Yes | |
features.inbound_transfers |
Object | No | |
features.inbound_transfers.ach |
Object | No | |
features.inbound_transfers.ach.requested |
Boolean | Yes | |
features.intra_stripe_flows |
Object | No | |
features.intra_stripe_flows.requested |
Boolean | Yes | |
features.deposit_insurance |
Object | No | |
features.deposit_insurance.requested |
Boolean | Yes | |
features.card_issuing |
Object | No | |
features.card_issuing.requested |
Boolean | Yes | |
features.outbound_transfers |
Object | No | |
features.outbound_transfers.us_domestic_wire |
Object | No | |
features.outbound_transfers.us_domestic_wire.requested |
Boolean | Yes | |
features.outbound_transfers.ach |
Object | No | |
features.outbound_transfers.ach.requested |
Boolean | Yes |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.