Issue Burner card with required parameters

Issue Burner Payment Card

The POST /api/paymentCards/orderBurnerPaymentCard endpoint issues a virtual burner payment card linked to a financial account. Burner cards are temporary, disposable payment instruments that expire automatically at the end of the following month or when a defined spending cap or transaction count is reached. They are designed to minimize exposure of primary payment methods during online purchases, trial subscriptions, or any limited-use scenario.

Endpoint

POST /api/paymentCards/orderBurnerPaymentCard

Authentication

Bearer token required. Obtain via:

POST https://api.banking.netevia.dev/api/auth/v2

Include in header: Authorization: Bearer {token}
Token lifetime: 10 minutes. Refresh via POST /api/auth/refresh.

When to use

Use this endpoint when a customer needs a short-lived, disposable payment card that limits financial exposure. Burner cards are ideal for online purchases, trial subscriptions, or any transaction where using a primary card would be a security risk. Once the card reaches its spending limit, transaction count, or expiration date, it deactivates automatically with no further action required.

Request Body

{
  "financialAccountId": "fa_9c3e21ab4d6f",
  "paymentCardName": "Trial Subscription Card",
  "expirationDate": "2026-07-31T23:59:59Z",
  "maxTotalSpending": 5000,
  "maxTransactionsCount": 3,
  "subProfileId": null
}

Response

200 OK

{
  "cardId": "pc_7f1a3bc29e45",
  "cardNumber": "XXXX-XXXX-XXXX-4821",
  "cvv": "***",
  "expirationDate": "2026-07-31T23:59:59Z",
  "status": "ACTIVE",
  "paymentCardName": "Trial Subscription Card",
  "financialAccountId": "fa_9c3e21ab4d6f"
}

Error Codes

Common Mistakes

• Omitting financialAccountId when the customer has multiple financial accounts — the API requires an explicit account reference.
• Setting maxTransactionsCount above 20 — the schema enforces a maximum of 20 transactions per burner card.
• Providing an expirationDate in the past or a format other than ISO 8601 date-time, which will cause a validation error.
• Passing subProfileId for a personal customer — authorized users (subProfiles) are a business-only feature.

Related Endpoints

• POST /api/paymentCards/orderVirtualPaymentCard — Issue a standard virtual card that does not expire automatically.
• POST /api/paymentCards/orderPhysicalPaymentCard — Order a physical (plastic) payment card shipped to the customer.
• GET /api/paymentCards/{paymentCardId} — Retrieve details and current status of an issued payment card.
• PUT /api/paymentCards/{paymentCardId}/cancel — Cancel or deactivate an existing payment card before its natural expiration.

Example

curl -X POST https://api.banking.netevia.dev/api/paymentCards/orderBurnerPaymentCard \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "financialAccountId": "fa_9c3e21ab4d6f",
    "paymentCardName": "Trial Subscription Card",
    "expirationDate": "2026-07-31T23:59:59Z",
    "maxTotalSpending": 5000,
    "maxTransactionsCount": 3,
    "subProfileId": null
  }'