Get Payment Cards List

This endpoint retrieves all payment cards linked to a given user profile, returning masked card numbers, expiration details, card types, and associated financial accounts. It supports both business and personal profile lookups, providing a complete snapshot of card inventory for a customer. The response includes spend rules, velocity rules, and card product information attached to each card.

Endpoint

GET /netevia/paymentCards/{profileId}

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 you need to display or audit all payment cards held by a customer, such as rendering a card management screen in your application. It is also useful for verifying which cards are active, suspended, or expired before processing a transaction or applying spend controls. Partners can call this endpoint to reconcile card issuance records or populate card selection interfaces.

Path Parameters

Response

200 OK

Returns an array of payment card objects. Each object contains the following fields:

cardProduct object fields:

[
  {
    "id": "card_abc123def456",
    "bin": "411111",
    "last4": "4242",
    "status": "ACTIVE",
    "formFactor": "VIRTUAL",
    "expirationDate": "2027-06",
    "expirationMonth": "06",
    "expirationYear": "2027",
    "network": "VISA",
    "cardType": 1,
    "cardProductName": "Business Rewards Visa",
    "cardProduct": {
      "name": "Business Rewards Visa",
      "id": "prod_xyz789",
      "usage": "BUSINESS",
      "productFundingAccounts": [
        {
          "id": "fa_001",
          "last4": "6789",
          "name": "Primary Checking",
          "type": "CHECKING",
          "accountStatus": "ACTIVE",
          "routingNumber": "021000021",
          "clientName": "Acme Corp"
        }
      ],
      "cardProfileSets": [
        {
          "id": "cps_001",
          "name": "Standard Profile Set",
          "intent": "SPEND",
          "network": "VISA",
          "status": "ACTIVE"
        }
      ]
    },
    "financialAccounts": [
      {
        "id": "fa_001",
        "name": "Primary Checking"
      }
    ],
    "subProfile": null,
    "subProfileId": null,
    "cardProfileSet": {
      "id": "cps_001",
      "name": "Standard Profile Set",
      "intent": "SPEND",
      "network": "VISA",
      "status": "ACTIVE"
    },
    "attachedSpendRules": {
      "pageInfo": {
        "startCursor": "cursor_start",
        "endCursor": "cursor_end",
        "hasNextPage": false,
        "hasPreviousPage": false
      },
      "edges": []
    },
    "attachedVelocityRules": {
      "pageInfo": {
        "startCursor": "cursor_start",
        "endCursor": "cursor_end",
        "hasNextPage": false,
        "hasPreviousPage": false
      },
      "edges": []
    }
  }
]

Error Codes

Common Mistakes

• Passing a non-integer or string value for profileId — the field must be a valid int32.
• Using an expired Bearer token; tokens expire after 10 minutes and must be refreshed before making the call.
• Expecting full card numbers in the response — only masked data (bin + last4) is returned; full PAN is never exposed via this endpoint.
• Confusing subProfileId with profileId — always supply the parent profile ID in the path, not a subprofile ID.

Related Endpoints

• POST /netevia/paymentCards — Issue a new payment card to a profile.
• GET /netevia/paymentCards/{profileId}/{cardId} — Retrieve details for a single payment card by card ID.
• PUT /netevia/paymentCards/{profileId}/{cardId} — Update status or settings of a specific payment card.
• GET /netevia/profiles/{profileId} — Retrieve the parent profile associated with the cards.

Example

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