Add a payment card

post

https://example.com/v1/payment-methods

Register a new payment card for the authenticated traveler using a client-side tokenized nonce (obtained after initialising the payment SDK with a token from POST /v1/payment-methods/client-token). Raw card data (PAN, CVV, expiry) is never accepted.

billingAddressId / invoiceProfileId optionally set the card's default billing references.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

Request body for POST /v1/payment-methods.

Carries only the Braintree tokenized nonce and a display name —
never PAN, CVV, or expiry. extra="forbid" rejects any unexpected
field so raw card data can never transit Mercury.

billing_address_id / invoice_profile_id are Mercury stable UUIDs
(from GET /v1/billing/addresses and the invoice-profile endpoints);
the route reverse-maps them to provider identifiers before forwarding.

nonce

string

required

length ≥ 1

Braintree payment-method nonce produced by client-side tokenization. Single-use; never a raw card number.

name

string

required

length ≥ 1

Display label for the card (shown in card selectors).

billingAddressId

Mercury billing-address UUID to set as the card default.

invoiceProfileId

Mercury invoice-profile UUID to set as the card default.

Responses

401

Missing or invalid authentication token, or the upstream rejected the forwarded credential while resolving billingAddressId / invoiceProfileId

403

Upstream refused the request despite a valid credential (resolved deny)

404

Billing address or invoice profile not found

422

Validation failed (unknown or missing fields)

502

Provider rejected the request (e.g. invalid nonce), or did not confirm the created payment method

503

Payment method service is temporarily unavailable

Language

Credentials

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

201Successful Response