Get Transaction Image
The Get Transaction Image endpoint retrieves an image that was uploaded and linked to a specific transaction. The image is returned as a base64-encoded string along with its content type (e.g., image/jpeg), allowing client applications to decode and render the image directly. This is useful for displaying transaction-related visuals in banking dashboards or transaction management interfaces.
Endpoint
GET /Files/transactionIcon
Authentication
Bearer token required. Obtain via:
POST https://api.banking.netevia.dev/api/auth/v2Include 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 an image associated with a transaction — for example, showing a merchant logo, receipt image, or other transaction-linked visual in a banking or financial management application. This endpoint is particularly valuable when building transaction detail views that require visual context to enhance transparency and clarity for end users.
Query Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| transactionId | string | Yes | The unique identifier of the transaction whose associated image you want to retrieve. |
Response
200 OK
| Field | Type | Description |
|---|---|---|
| Content | string | The transaction image encoded as a base64 string. Decode this value to render the image. |
| ContentType | string | The MIME type of the image (e.g., image/jpeg, image/png). Use this to correctly interpret and display the image data. |
{
"Content": "/9j/4AAQSkZJRgABAQEASABIAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8U...",
"ContentType": "image/jpeg"
}Error Codes
| Code | When it happens |
|---|---|
| 400 | The transactionId query parameter is missing or malformed. |
| 401 | Token missing, expired, or invalid. |
| 403 | Insufficient permissions to access the specified transaction's image. |
| 404 | No image is linked to the provided transactionId. |
| 500 | Internal server error. |
Common Mistakes
- Omitting the
transactionIdquery parameter entirely — this is a required parameter and the request will fail without it. - Not specifying the correct
transactionId— ensure you are passing the transaction's unique identifier, not a payment ID or account ID. - Forgetting to base64-decode the
Contentfield before attempting to display the image — the returned string is encoded and must be decoded first. - Ignoring the
ContentTypefield — always use the returned MIME type to correctly handle and render the image in your UI.
Related Endpoints
POST /Files/transactionIcon— Upload or associate an image with a specific transaction.GET /Files/profileIcon/{profileId}— Retrieve the profile image for a customer.
Example
curl -X GET "https://api.banking.netevia.dev/Files/transactionIcon?transactionId=txn_abc123456789" \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Accept: application/json"return content of your image