Submit Bulk Transfer
- Paymish
- Transfer
Submit Bulk Transfer
Endpoint to submit a bulk transfer request
Purpose
Use this endpoint to submit bulk transfer. It belongs to the Transfer collection and is designed for backend integrations.
Request shape
0 parameters and
3 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 POST 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 the request payload on your backend before sending it, especially the 3 documented body fields.
- Protect state-changing operations with strong validation, logging, and retry rules to avoid duplicate mutations.
Request Body
Content type: application/json
debitBankCode
required
998
debitAccountNumber
required
0112345678
data
required
Responses
Expected Outcomes
Transfer accepted
Successfully submitted bulk transfer
{
"message": "Bulk transfer successfully submitted",
"transactionId": "txn_123456789"
}
Transfer blocked
Bad request due to invalid input
{
"error": "Invalid request payload"
}
- Do not create a fresh reference automatically during a retry unless you intentionally want a new payout attempt.
- Check recipient validation, approval state, and balance rules before resubmitting the transfer.
- Monitor the stored transfer reference after a successful initiation because final payout state may still transition later.
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",
"Content-Type": "application/json",
}
payload = {
"debitBankCode": "998",
"debitAccountNumber": "0112345678",
"data": "value"
}
response = requests.post(
"https://api.paymish.com/api/transaction-service/external/v1/transfer/submit-bulk-transfer",
headers=headers,
json=payload,
)
data = response.json()
print(data)
const axios = require("axios");
const response = await axios({
method: "post",
url: "https://api.paymish.com/api/transaction-service/external/v1/transfer/submit-bulk-transfer",
headers: {
Authorization: "Bearer YOUR_SECRET_KEY",
"Content-Type": "application/json",
},
data: {
"debitBankCode": "998",
"debitAccountNumber": "0112345678",
"data": "value"
}
});
console.log(response.data);
curl https://api.paymish.com/api/transaction-service/external/v1/transfer/submit-bulk-transfer \
-X POST \
-H "Authorization: Bearer YOUR_SECRET_KEY" \
-H "Content-Type: application/json" \
-d '{ "debitBankCode": "998", "debitAccountNumber": "0112345678", "data": "value" }'
<?php
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, "https://api.paymish.com/api/transaction-service/external/v1/transfer/submit-bulk-transfer");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, "POST");
curl_setopt($ch, CURLOPT_HTTPHEADER, [
"Authorization: Bearer YOUR_SECRET_KEY",
"Content-Type: application/json",
]);
curl_setopt($ch, CURLOPT_POSTFIELDS, json_encode([
"debitBankCode" => "998",
"debitAccountNumber" => "0112345678",
"data" => "value",
]));
$response = curl_exec($ch);
curl_close($ch);
$data = json_decode($response, true);
print_r($data);