Saved Cards

Orders paid with payment.method: "saved_card" charge a card that was previously vaulted for your organization. The Partner API never accepts raw card data; it only consumes a savedCardId.

Card Lifecycle

1. Vaulting -- A card is registered through the partner dashboard web application. The registration runs a one-time card verification with 3D Secure through the payment provider (NestPay); the card details go directly to the provider and are stored as a vault token. Card vaulting is not available on the API-key surface.
2. Usage -- After vaulting, the dashboard shows the card's savedCardId (a UUID). Pass it as payment.savedCardId when creating orders. Charges made this way do not require the cardholder to be present.
3. Removal -- Cards can be removed in the partner dashboard. Orders referencing a removed card fail with 404.

Rules

• savedCardId must belong to your organization. Unknown or foreign IDs return 404 and no idempotency claim is burned.
• savedCardId is required when payment.method is saved_card; omitting it returns 400.
• In sandbox mode the card is not charged; any well-formed request is approved with a simulated result.

For request and response details, see Create Order.