Skip to main content
POST
Start an ACH bank-account setup (Stripe Financial Connections)
Portal endpoints authenticate via the portal_session cookie issued by magic-link verification — not a Bearer API key. State-changing portal calls must additionally echo the portal_csrf cookie’s value in the X-CSRF-Token header (double-submit CSRF).
Creates a us_bank_account SetupIntent via Stripe Financial Connections for the authenticated portal customer (instant bank verification) and returns the client_secret the browser’s collectBankAccountForSetup confirms, plus the publishable key. Bank data goes browser → Stripe directly — none of it reaches Recurso. After the browser confirms the SetupIntent, finalize the saved account with POST /portal/api/payment-method/confirm. Returns 503 on deployments where Stripe/ACH is unavailable.

Example Request

Response

For card updates use Start Card Update instead; both flows finalize through the same confirm endpoint.

Authorizations

portal_session
string
cookie
required

Customer-portal session cookie issued by GET /portal/auth/verify.

Response

Bank-account SetupIntent created.

data
object