Skip to main content
POST
Step 2 -- Attach a confirmed Stripe PaymentMethod to the account

Authorizations

Authorization
string
header
required

API key issued per entity via Settings > Developers > API Keys. Each key carries scopes (e.g. orders:read, products:write). Bearer token format: Authorization: Bearer ark_live_ent_Test keys use ark_test_ent_. Both are issued per entity
via Settings > Developers > API Keys.

Headers

Idempotency-Key
string

Client-generated unique key for idempotent POST/PATCH/DELETE operations. Alias for the Idempotency parameter. Max 255 chars. On retry with the same key, the original response is returned without re-executing the operation. Keys expire after 24 hours.

Maximum string length: 255

Path Parameters

id
string<uuid>
required

Account ID

pm_id
string
required

Stripe PaymentMethod ID (e.g. pm_xyz)

Body

application/json
save_for_future
boolean
default:true

Response

Payment method attached

A reusable payment instrument stored on an account (card, ACH bank account, etc.).

id
string<uuid>
object
enum<string>
Available options:
payment_method
account_id
string<uuid>
method_type
enum<string>
Available options:
credit_card,
debit_card,
ach,
wire,
check_on_file,
store_credit
is_default
boolean
is_verified
boolean

ACH microdeposit-verified or card-AVS-verified.

last4
string | null
brand
string | null

visa, mastercard, amex, etc.

exp_month
integer | null
exp_year
integer | null
bank_name
string | null
account_type
string | null

checking / savings (ACH only).

stripe_payment_method_id
string | null
read-only
created_at
string<date-time>
read-only