Skip to main content
Use this flow when you need to create a stored card payment method from raw card data. Send the request to https://secure-api.montereyfinancial.app, not api.montereyfinancial.app.
Never send PAN or CVC to api.montereyfinancial.app. Raw card data belongs on https://secure-api.montereyfinancial.app only.
Availability is environment-specific. Until Monterey enables secure capture for your environment, this endpoint may return 503.

Before you call

  • An API key that can mint an access token
  • The payment_methods:write scope
  • curl and jq
  • A Basis Theory test card supported by your environment
This page documents the request shape. It does not verify which test cards your Basis Theory environment has enabled.

Choose the borrower

party_id must be visible to the token and attached to the account.

Choose the billing address

Send at most one of billing_address_id or billing_address. Omit both to use the selected borrower’s current billing address. The inline address is transient and does not create a new saved party address.

Create the card payment method

Replace the card fields with a test card supported by your Basis Theory environment. Omit party_id if you want Monterey to use the account’s primary borrower. Swap billing_address_id for billing_address if you need a transient address for this request.

Retry behavior

Retry only the exact same request body with the same Idempotency-Key.

Authentication

Exchange your API key for an access token and use it on the secure proxy.

Conventions

Read the shared rate-limit, idempotency, and error rules.

Domain concepts

See how parties, accounts, payment methods, and billing addresses fit together.