Retrieve Subscription Transactions for a Payment Card

This endpoint returns a list of subscription-related transactions for a given payment card, identified by its unique paymentCardId. Each transaction record includes status, timestamps, requester details, and linked financial account and card metadata. It is useful for auditing recurring payment activity or surfacing subscription history within a partner-facing application.

Endpoint

GET /subscriptions/{paymentCardId}/transactions

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 the subscription transaction history tied to a specific payment card — for example, to show a cardholder their recurring charges, or to allow an admin to investigate subscription activity. It supports optional name-based filtering to narrow results to a particular subscription service or requester.

Path Parameters

Query Parameters

Response

200 OK

The response is an array of subscription transaction objects. Each object includes the following fields:

Transaction Object (carddigitalwallettokenresponse)

Nested paymentCard Object

[
  {
    "id": "sub_txn_a1b2c3d4e5",
    "status": "Completed",
    "createdAt": "2025-07-15T13:42:00Z",
    "updatedAt": "2025-07-15T13:45:00Z",
    "requesterName": "Acme Subscriptions Inc.",
    "financialAccount": "fa_9988776655",
    "financialName": "Business Checking",
    "financialNumber": "XXXXXXXXXX",
    "iconUrl": "https://cdn.example.com/icons/acme.png",
    "paymentCard": {
      "id": "card_112233445566",
      "expirationDate": "2027-08",
      "last4": "4321",
      "cardholder": "Jane Doe",
      "authorizedUser": null,
      "departament": "Operations",
      "cardName": "Operations Card",
      "partnerName": "Netevia",
      "formFactor": "Virtual",
      "status": "Active"
    }
  }
]

Error Codes

Common Mistakes

• Passing an incorrect or non-existent paymentCardId — verify the card ID exists and belongs to the authenticated customer before calling this endpoint.
• Expecting financialNumber to return a full unmasked account number — it is masked in display contexts; handle accordingly in your UI.
• Omitting the Authorization header or using an expired token — tokens expire after 10 minutes; refresh proactively using POST /api/auth/refresh.
• Treating the filterName parameter as case-sensitive or expecting exact-match behavior — validate the filter logic in your environment before relying on it in production.

Related Endpoints

• GET /subscriptions/{paymentCardId} — Retrieve subscription details for a specific payment card
• GET /subscriptions — List all subscriptions for the authenticated customer
• GET /payment-cards/{paymentCardId} — Retrieve details of a specific payment card

Example

curl -X GET "https://api.banking.netevia.dev/subscriptions/card_112233445566/transactions?filterName=Acme" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json"