Resolve Account Number
- Paymish
- Banks
Resolve Account Number
Confirms that an account number exists at a bank and returns the account holder's name. Use it to show customers the name before they confirm a payout, or to validate recipient details. **Live keys (`sk_live_*`)** - no lookup limit. **Test keys (`sk_test_*`)** - lookups are real, but limited to **10 per day** per business. The count resets at 00:00 UTC. Every test-mode response carries `X-RateLimit-Limit`, `X-RateLimit-Remaining` and `X-RateLimit-Reset` (Unix seconds) so you can see where you stand. Once the limit is reached you get a `429` until the reset; switch to a live key for unlimited lookups. Requests rejected for bad parameters (`400`) and lookups that fail on our side (`503`) do not count against the limit.
Purpose
Use this endpoint to retrieve resolve account number. It belongs to the Banks collection and is designed for backend integrations.
Request shape
2 parameters and
0 documented body fields
using application/json.
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
- Validate and encode query parameters before sending them so filters and pagination behave predictably.
Query Parameters
account_number
required
bank_code
required
Responses
Expected Outcomes
Success example
Account number resolved
{
"status": "success",
"message": "Record retrieved successfully",
"data": {
"reference": "PM-REF-12345",
"status": "success"
}
}Record not found
The bank could not match that account number
{
"status": "error",
"message": "Requested record was not found.",
"errors": {
"reference": [
"Check the identifier and merchant context before retrying."
]
}
}- Log the Paymish reference or request context returned by the API so support teams can trace the call later.
- Retry only when the failure is safe to repeat; otherwise correct the payload or auth state first.
- Store enough internal metadata to match the API response back to your order, payout, case, or checkout record.
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/bank/resolve",
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/bank/resolve",
headers: {
Authorization: "Bearer YOUR_SECRET_KEY",
}
});
console.log(response.data);curl https://api.paymish.com/api/transaction-service/external/v1/bank/resolve \
\
-H "Authorization: Bearer YOUR_SECRET_KEY"<?php
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, "https://api.paymish.com/api/transaction-service/external/v1/bank/resolve");
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);