DEMOFILE APP • Deposit & Payout

Deposit Flow

1) Create deposit → 2) Redirect user to payment URL → 3) Verify callback

Endpoint: POST /api/v1/deposit → response returns a hosted payment url you redirect your customer to.

merchant_account required

merchant_order required

merchant_user_unique_id required

product_desc required

first_name required

last_name required

address required

city required

zip_code required

country (ISO-2) required

phone required

email required

ip_address required

amount (non-floating) required

Example from docs: 100075 represents 1000.75.

currency required

status_callback_url optional

redirect_back_url required

control (HMAC-SHA1) required

Control checksum uses HMAC-SHA1 over: (merchant_account + amount + currency + first_name + last_name + address + city + zip_code + country + phone + email + merchant_order + product_desc + redirect_back_url).

Tip: Generate control before sending. In production, generate control on your server (never in the browser).

Request & Response

Live preview

Deposit request JSON

{}

API response

—

Verify Deposit Callback

Paste the JSON you receive at your callback URL

Callback checksum: HMAC-SHA1(transaction_id + merchant_order + amount + currency + bank_transaction_id + status, partner_control)

Callback JSON

Result

—

Withdrawal / Payout Flow

1) Create payout → 2) Track status → 3) Verify callback

Endpoint: POST /api/v1/payout. You must supply bank_code (use the built-in bank picker) and a control checksum (SHA1).

merchant_account required

merchant_order required

customer_name required

For checksum generation, this field is Base64-encoded.

currency required

amount (non-floating) required

bank_code required

bank_account_number required

bank_province_code required

bank_city_code required

bank_branch_address required

memo optional

id_number Pakistan only

status_callback_url optional

control (SHA1) required

Control checksum uses SHA1 over: (merchant_account + merchant_order + amount + currency + Base64(customer_name) + bank_code + bank_account_number + partner_control)

Tip: bank_code is auto-filled from the bank picker (read-only). For INR, select a prefix then enter the full IFSC in the prompt (e.g. HDFC0003083).

Request & Response

Live preview

Payout request JSON

{}

API response

—

Verify Payout Callback

Paste the JSON you receive at your callback URL

Callback checksum: SHA1(transaction_id + merchant_account + merchant_order + amount + currency + status + partner_control)

Callback JSON

Result

—

Pick a Bank Code

Click a bank row to apply it to bank_code

Country / Rail

Philippines payouts: send bank_code exactly as shown (e.g. ALKBPHM2XXX, GXCHPHM2XXX). No SPP_ prefix.

Code	Name

Bank Codes Reference

Searchable list (embedded fallback) + live refresh from GlobaltechPay docs

Use this list for selecting bank_code in payouts. For PHP payouts, send the Bank Code column value directly (e.g. ALKBPHM2XXX, AUBKPHMMXXX, MRTCPHM1XXX).

Data source: embedded

This app will try to fetch updated bank codes from apidoc.globaltechpay.com/bank-codes. If CORS/network blocks it, it will use the embedded list.

Country / Rail

Code	Name	Payout bank_code

India (INR) note

For INR payouts, GlobaltechPay expects the full IFSC code (example: HDFC0003083). This page includes an IFSC prefix list to guide selection.

Saved Settings

This page stores values in your browser localStorage so you can reload quickly.

API Base URL

Deposit merchant_account

Payout merchant_account

Deposit partner_control (shared secret)

Payout partner_control (shared secret)

Security reminder

The docs explicitly warn: never expose your partner_control. This HTML computes checksums in-browser for convenience and testing. In a real integration, generate control on your server and never ship the secret to the client.

Docs & Flow References

This demo UI is designed to align with the official GlobaltechPay documentation pages below.

Resource	Link
Deposit API	apidoc.globaltechpay.com/deposit-api ↗
Payout API	apidoc.globaltechpay.com/payout-api ↗
Bank Codes	apidoc.globaltechpay.com/bank-codes ↗

CORS note: Calling the APIs (and docs pages) directly from a browser may fail if the server does not allow cross-origin requests. If that happens, run this page behind your own backend and proxy the requests server-side.