Paymish Loading Docs Preparing guides, collections, and live API references...
Paymish Docs

Retrieve the list of banks.

Endpoint Overview

GET /api/transaction-service/external/v1/transfer/all-banks

Purpose

Use this endpoint to retrieve the list of banks. It belongs to the Transfer collection and is designed for backend integrations.

Request shape

0 parameters and 0 documented body fields using application/json.

Implementation Guide

Recommended workflow

1

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

2

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

3

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

Implementation notes

  • This is a read-oriented endpoint, so focus on validating inputs, handling auth, and storing the returned data safely.

Responses

200 A list of banks retrieved successfully.
400 Bad request due to missing or invalid parameters.
404 The requested list of banks could not be found.
500 Internal server error.

Expected Outcomes

200

Success example

A list of banks retrieved successfully.

Representative Response
{
  "status": "success",
  "message": "Record retrieved successfully",
  "data": {
    "reference": "PM-REF-12345",
    "status": "success"
  }
}
404

Record not found

Bad request due to missing or invalid parameters.

Representative Error
{
  "status": "error",
  "message": "Requested record was not found.",
  "errors": {
    "reference": [
      "Check the identifier and merchant context before retrying."
    ]
  }
}
After the response:
  • 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

Python
import requests

headers = {
}
response = requests.get(
    "https://api.paymish.com/api/transaction-service/external/v1/transfer/all-banks",
    headers=headers,
)

data = response.json()
print(data)
Node.js
const axios = require("axios");

const response = await axios({
  method: "get",
  url: "https://api.paymish.com/api/transaction-service/external/v1/transfer/all-banks",
  headers: {
  }
});

console.log(response.data);
cURL
curl https://api.paymish.com/api/transaction-service/external/v1/transfer/all-banks \
PHP
<?php
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, "https://api.paymish.com/api/transaction-service/external/v1/transfer/all-banks");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, "GET");
curl_setopt($ch, CURLOPT_HTTPHEADER, [

]);

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