/subscriptions/{paymentCardId}/transactions

API Method: GET /subscriptions/{paymentCardId}/transactions

**Description:**This endpoint retrieves a list of subscription-related transactions for a specific payment card. It is useful for reviewing activity tied to recurring payments (subscriptions) made with a card. Each transaction entry includes metadata such as status, timestamps, and the name of the requester (the entity that initiated the transaction).

This API is typically used in scenarios where a user, admin, or auditor needs to track and filter recurring transaction activity associated with a specific payment card.


Request:

  • Method: GET

  • Endpoint: https://api.banking.netevia.dev/subscriptions/{paymentCardId}/transactions

  • Headers:

    • Authorization: Bearer <access_token> (required)
    • Content-Type: application/json

Path Parameters:

  • paymentCardId (string, required) – The ID of the payment card whose subscription transactions are being requested.

Query Parameters:

  • filterName (string, optional) – A filter to narrow results by requester name or other internal criteria (exact filter logic depends on implementation).

Response:

  • Status Code: 200 OK
  • Content Type: application/json
  • Response Body: A list of subscription transaction objects.
[
  {
    "id": "string",
    "status": "string",
    "createdAt": "string",
    "updatedAt": "string",
    "requesterName": "string"
  }
]

Fields:

  • id (string) – Unique identifier for the transaction
  • status (string) – Current status of the transaction (e.g., "Completed", "Pending", "Failed")
  • createdAt (string) – ISO timestamp of when the transaction was created
  • updatedAt (string) – ISO timestamp of the last update to the transaction
  • requesterName (string) – The name of the user or service that initiated the transaction

Example Response:

[
  {
    "id": "txn_987654321",
    "status": "Completed",
    "createdAt": "2025-07-15T13:42:00Z",
    "updatedAt": "2025-07-15T13:45:00Z",
    "requesterName": "Acme Subscriptions Inc."
  }
]

Error Responses:

  • 400 Bad Request – Invalid paymentCardId or query format
  • 401 Unauthorized – Missing or invalid access token
  • 404 Not Found – No transactions found for the specified card
  • 500 Internal Server Error – Server encountered an error while processing the request

Notes:

  • Only users with permission to view the card's subscription history should access this endpoint.
  • Use filterName to narrow the results to specific subscription services or requesters.
Language
Credentials
Bearer
JWT
Click Try It! to start a request and see the response here!