List Payment Card Shipping Methods

The /api/enums/paymentCardShippingMethod endpoint returns all supported shipping methods for payment card delivery. Use this endpoint to populate shipping method selection in your frontend during card issuance or card replacement flows. The response provides enumerated values with human-readable descriptions that can be displayed directly to end customers.

Endpoint

GET /api/enums/paymentCardShippingMethod

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

Call this endpoint before presenting a card order or card replacement form to a customer so the UI can display the current list of available shipping options. The returned enum values should be passed as the shipping method field when creating or updating a card issuance request. Refreshing this list periodically ensures your integration reflects any newly supported delivery tiers.

Response

200 OK

Returns an array of enum description objects.

[
  {
    "name": "STANDARD",
    "id": 1,
    "description": "Standard Delivery (5-7 business days)",
    "groupName": "Shipping",
    "endpoints": [
      "/api/cards/physical/issue",
      "/api/cards/physical/replace"
    ]
  },
  {
    "name": "EXPRESS",
    "id": 2,
    "description": "Express Delivery (2-3 business days)",
    "groupName": "Shipping",
    "endpoints": [
      "/api/cards/physical/issue",
      "/api/cards/physical/replace"
    ]
  },
  {
    "name": "OVERNIGHT",
    "id": 3,
    "description": "Overnight Delivery (next business day)",
    "groupName": "Shipping",
    "endpoints": [
      "/api/cards/physical/issue",
      "/api/cards/physical/replace"
    ]
  }
]

Error Codes

Common Mistakes

• Hardcoding shipping method IDs in your integration instead of fetching them from this endpoint — IDs may change or new methods may be added; always use the live list.
• Displaying the name field directly to customers instead of the description field — name is the machine-readable enum key while description is intended for user-facing text.
• Skipping this call and assuming a fixed set of options — available shipping methods may vary by partner configuration or region.

Related Endpoints

• GET /api/enums/paymentCardStatus — Retrieve all valid payment card status enum values
• GET /api/enums/paymentCardType — Retrieve all valid payment card type enum values (Physical, Virtual, Burner)
• POST /api/cards/physical/issue — Issue a new physical card, requires a valid shipping method id from this endpoint

Example

curl -X GET https://api.banking.netevia.dev/api/enums/paymentCardShippingMethod \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json"