Verify Transaction.

Paymish Docs

Verify Transaction.

Paymish
Transaction

Endpoint Overview

GET /api/transaction-service/external/v1/verify/{reference} Requires authentication

Purpose

Use this endpoint to retrieve verify transaction. It belongs to the Transaction collection and is designed for backend integrations.

Request shape

1 parameter and 0 documented body fields using application/json.

Implementation Guide

Recommended workflow

Authenticate first and inject a valid bearer token or secret key before calling the endpoint.

Validate the input data, identifiers, and account state in your application before making the request.

Send the GET request from your backend using the required headers and the expected content type (application/json).

Persist the important identifiers returned in the response so later lookups, webhooks, or support actions can be linked correctly.

Implementation notes

Construct path parameters carefully and avoid string concatenation mistakes when building the final URL.

Path Parameters

reference required

string

The transaction reference used to initiate the transaction.

Responses

200 Transaction verified successfully.

400 Bad request - Transaction reference is required.

404 Transaction not found.

500 Internal server error.

Expected Outcomes

Transaction verified successfully.

{
  "status": "success",
  "data": "value",
  "message": "Transaction verified successfully"
}

Bad request - Transaction reference is required.

{
  "status": "error",
  "error": "Transaction not found"
}

After the response:

Confirm you are verifying the exact stored Paymish reference from the original checkout attempt.
Use verification results to update your internal order or invoice state instead of trusting redirect-only status.
Retry only after confirming the payment attempt has had enough time to settle or after receiving the relevant webhook update.

Language Notes

Python

Use `requests` from a backend worker, service, or Django/Flask app and centralize headers in a reusable helper.

Node.js

Use `axios` or `fetch` from Node.js services only; do not place secret credentials in frontend bundles.

PHP

Wrap cURL usage in a small client class so auth headers, error handling, and logging stay consistent.

cURL

Use cURL for smoke testing and debugging, then move the final logic into your backend service code.

Code Examples

import requests

headers = {
    "Authorization": "Bearer YOUR_SECRET_KEY",
}
response = requests.get(
    "https://api.paymish.com/api/transaction-service/external/v1/verify/{reference}",
    headers=headers,
)

data = response.json()
print(data)

const axios = require("axios");

const response = await axios({
  method: "get",
  url: "https://api.paymish.com/api/transaction-service/external/v1/verify/{reference}",
  headers: {
    Authorization: "Bearer YOUR_SECRET_KEY",
  }
});

console.log(response.data);

curl https://api.paymish.com/api/transaction-service/external/v1/verify/{reference} \
   \
  -H "Authorization: Bearer YOUR_SECRET_KEY"

<?php
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, "https://api.paymish.com/api/transaction-service/external/v1/verify/{reference}");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, "GET");
curl_setopt($ch, CURLOPT_HTTPHEADER, [
    "Authorization: Bearer YOUR_SECRET_KEY",
]);

$response = curl_exec($ch);
curl_close($ch);
$data = json_decode($response, true);
print_r($data);

Previous endpoint Create a Dedicated Virtual Account.