Legacy

Use Treasury for platforms and Issuing to set up financial accounts and cards Legacy

Follow a sample Treasury for platforms and Issuing integration that sets up a financial account and creates cards.

Legacy integration

The v1 version of Treasury for platforms is a legacy integration that doesn’t support many of the features introduced in Treasury for platforms v2. Don’t build a new v1 integration.

Homebox is a fictitious vertical SaaS that builds software for home-services companies like the related setting technicians, cleaners, and plumbers. Homebox begins its Treasury for platforms integration by setting up a financial account and creating payment cards. To see how Homebox moves money to and from external bank accounts, see the Using Treasury for platforms to move money example integration.

Platform onboarding

Homebox is already a Stripe platform with Payments and Connect enabled. Homebox uses Custom connected accounts, and those connected accounts already have the card_payments capability enabled.

Add capabilities

Accounts v2 API compatibility

The Accounts v2 API doesn’t support Treasury for platforms workflows. If you have accounts created with Accounts v2, you can use Accounts v1 to manage the treasury and card_issuing capabilities. For details, see Use Accounts as customers.

To use Treasury for platforms and Issuing services, Homebox needs to request the additional treasury and card_issuing capabilities for the platform’s connected accounts. Each connected account must then onboard before Stripe can create a financial account for it.

To use ACH transfers with Treasury for platforms, Homebox also needs to request the us_bank_account_ach_payments capability.

To request the treasury, card_issuing, and us_bank_account_ach_payments capabilities, Homebox makes a request to the Accounts API.

Command Line

Select a language

cURL

Stripe CLI

Ruby

Python

PHP

Java

Node.js

Go

.NET

No results

To use Hosted Onboarding, Homebox makes a call to Account Links to retrieve a URL that their connected account can use to submit onboarding information for the financial account.

Command Line

Select a language

cURL

Stripe CLI

Ruby

Python

PHP

Java

Node.js

Go

.NET

No results

The response includes a URL the connected account uses to access the application, which must be done before the link expires.

Homebox listens for the account.updated webhook to confirm the following fields and capabilities on the connected account:

{
 "object": {
 "id": "{{CONNECTED_ACCOUNT_ID}}",
 "object": "account",
 "capabilities": {
 "card_payments": "active",
 "treasury": "active",
 "card_issuing": "active", // Only appears if requesting the `card_issuing` capability.
 "us_bank_account_ach_payments": "active", // Only appears if requesting the `us_bank_account_ach_payments` capability.
 },
 ...
 }
}

Create a FinancialAccount

After Stripe adds the treasury capability to an account, Homebox can create the FinancialAccount object for the account. To do so, Homebox calls the Financial Accounts API and requests the Features the company wants to provide.

Command Line

Select a language

cURL

Stripe CLI

Ruby

Python

PHP

Java

Node.js

Go

.NET

No results

The response confirms the account is processing. After processing completes and all relevant features are active, Homebox gets a confirmation from their treasury.financial_account.features_status_updated webhook listener.

{
 "object": "treasury.financial_account",
 "created": 1612927106,
 "id": "{{FINANCIAL_ACCOUNT_ID}}",
 "country": "US",
 "supported_currencies": ["usd"],
 "financial_addresses": [ // This field is empty until the "financial_addresses.aba" feature becomes active
 {
 "type": "aba",
 "supported_networks": ["ach", "us_domestic_wire", "rtp"],
 "aba": {
 "account_number_last4": "7890",
 // The full account_number is only returned if the request expands it.
 "account_number": "1234567890",
 "routing_number": "000000001",
 "bank_name": "Bank of Earth"
 }
 }
 ],
 "livemode": true,

 // State machine:
 // open - the account is ready to be used
 // closed - the account is closed
 "status": "open",
 "status_details": {
 // `closed` is null if financial account is not closed
 "closed": {
 // List of one or more reasons why the FinancialAccount was closed:
 // - account_rejected
 // - closed_by_platform
 // - other
 "reasons": []
 }
 },

 "active_features": ["card_issuing"],
 "pending_features": ["deposit_insurance", "financial_addresses.aba", "outbound_payments.ach", "us_domestic_wire", "inbound_transfers.ach", "outbound_transfers.ach", "outbound_transfers.us_domestic_wire"],
 "restricted_features": [],

 "features": {
 "object": "treasury.financial_account_features",
 "card_issuing": {
 "status": "active",
 "status_details": [],
 "access": "active"
 },
 "deposit_insurance": {
 "requested": true,
 "status": "pending", // Becomes "active" after the financial account is set up
 "status_details": [{"code": "activating", "resolution": null}]
 },
 "financial_addresses": {
 "aba": {
 "requested": true,
 "status": "pending", // Becomes "active" after the financial account is set up
 "status_details": [{"code": "activating", "resolution": null}]
 }
 },
 "outbound_payments": {
 "ach": {
 "requested": true,
 "status": "pending", // Becomes "active" after the financial account is set up
 "status_details": [{"code": "activating", "resolution": null}]
 },
 "us_domestic_wire": {
 "requested": true,
 "status": "pending", // Becomes "active" after the financial account is set up
 "status_details": [{"code": "activating", "resolution": null}]
 }
 },
 "inbound_transfers": {
 "ach": {
 "requested": true,
 "status": "pending", // Becomes "active" after the financial account is set up
 "status_details": [{"code": "activating", "resolution": null}]
 }
 },
 "outbound_transfers": {
 "ach": {
 "requested": true,
 "status": "pending", // Becomes "active" after the financial account is set up
 "status_details": [{"code": "activating", "resolution": null}]
 },
 "us_domestic_wire": {
 "requested": true,
 "status": "pending", // Becomes "active" after the financial account is set up
 "status_details": [{"code": "activating", "resolution": null}]
 }
 }
 },
 "platform_restrictions": {
 "inbound_flows": "unrestricted",
 "outbound_flows": "unrestricted"
 },
 "metadata": {},
 ...
}

Create a payment cardholder

Before Homebox can create cards for financial accounts, it needs to create cardholders. The cardholders in this example are plumbers who use Homebox services and own the connected accounts on the platform.

1. Visit the Connected accounts page in the Dashboard.
2. Select the connected account you want to create a cardholder on to expand its details.
3. Select the Card issuing tab.
4. Click the + button next to Cardholders .
5. Fill in the cardholder’s details and click Create cardholder .

Create payment cards

Now that the connected account has a FinancialAccount object associated with it and an available cardholder, Homebox can create a payment card using the FinancialAccount balance as the card’s available balance.

Note

You can’t create Financial accounts in the Dashboard. You must use the API to create them.

1. Visit the Connected accounts page in the Dashboard.
2. Select the connected account you want to create a cardholder on to expand its details.
3. Select the Card issuing tab.
4. Click the + button next to Cards .
5. Select the card type and the financial account that you want to fund the card with and click Create .

See also

• Using Treasury for platforms to move money
• API reference