Transfer between accounts (PG or cross-channel)
Transfers funds from the given PG account (remitter) to a beneficiary under the same merchant. Compatible-extend contract: omit beneficiary_channel (or set PG) and pass beneficiary_account_number for intra-PG movement; set beneficiary_channel=KYC to credit the merchant KYC credit-pool. BILLER is reserved. Requires request signature headers (verify.signature-internal).
Idempotency: send an optional merchant_ref_no unique per merchant. If a value already used by the same merchant is submitted again, the original transfer is returned (HTTP 200) and no new movement is created — regardless of which of the merchant’s accounts is the remitter. If merchant_ref_no is omitted or empty, the platform auto-generates a unique reference (format AM-<timestamp>-<random>) and returns it in the response.
Authorizations
Body
Compatible-extend contract: PG→PG still uses beneficiary_account_number. Cross-channel (KYC / future BILLER) sets beneficiary_channel and omits the PG account number. Optional beneficiary_account_id is reserved for multi-pool peer products.
Optional merchant-supplied idempotency reference. Unique per merchant across all account movements: reusing a value already used by the same merchant returns the original transfer (HTTP 200) without creating a duplicate. If omitted or empty, the platform auto-generates a unique reference (format AM-<timestamp>-<random>) and returns it in the response — a generated reference is unique per request and therefore provides no replay protection. A different merchant may reuse the same value.
191"MOVE-20260702-001"
Response
Transfer completed successfully. The data object contains the created transfer record.
