Set user's memo for card's transaction by ID

Set Transaction Memo

The Set Transaction Memo endpoint allows authenticated users to attach or update a custom text memo on a specific card transaction. By providing the payment card ID and transaction ID, users can annotate individual transactions for improved record-keeping and categorization. The memo does not alter the original transaction data — it only adds a user-defined note to the transaction record.

Endpoint

POST /api/transaction/setTransactionMemo

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 cardholder or authorized user needs to add a note or label to a transaction for personal tracking or accounting purposes. This is particularly useful in business contexts where users categorize expenses or flag transactions for review. The memo can also be cleared or overwritten by calling the endpoint again with an empty or updated value.

Request Body

{
  "paymentCardId": "card-a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "transactionId": "txn-9f8e7d6c-5b4a-3210-fedc-ba9876543210",
  "memo": "Client lunch Q2 2026"
}

Response

200 OK

A 200 status code indicates the memo was successfully set or updated on the transaction. The response body is empty on success.

{}

Error Codes

Common Mistakes

• Omitting paymentCardId or transactionId — both are required fields; the request will be rejected with a 400 error if either is missing or empty.
• Submitting a memo value longer than 30 characters — the schema enforces a maximum length of 30 and will reject values that exceed it.
• Using a transactionId that does not belong to the card identified by paymentCardId — ensure both IDs correspond to the same transaction record.
• Attempting to set a memo on a transaction belonging to a card the authenticated user does not own or have access to — this will result in a 403 error.

Related Endpoints

• GET /api/transaction/getTransactionDetails — Retrieve full details of a specific transaction, including any existing memo
• GET /api/transaction/getTransactionList — List transactions for a payment card
• POST /api/transaction/getTransactionListByDateRange — Query transactions within a specified date range

Example

curl -X POST https://api.banking.netevia.dev/api/transaction/setTransactionMemo \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "paymentCardId": "card-a1b2c3d4-e5f6-7890-abcd-ef1234567890",
    "transactionId": "txn-9f8e7d6c-5b4a-3210-fedc-ba9876543210",
    "memo": "Client lunch Q2 2026"
  }'