Skip to main content

8. MYR P2P shop fields

The method in a v2 create request selects your merchant shop. Use the code supplied during onboarding. The table describes the MYR P2P shop fields by operation.

OperationJSON fieldTypeRequiredMeaning
Depositfields.wallet_providerstringYesWallet provider code enabled for the shop.
Depositfields.bank_codestringYesBank code supplied for the selected shop.
Withdrawalfields.bank_codestringOptionalCode for the recipient's bank.
Withdrawalfields.holderstringOptionalName of the recipient account holder.

Both deposit values must be present in one JSON object. Obtain the supported values from your integration contact and preserve their spelling. WALLET_CODE and BANK_CODE below are placeholders.

{
"fields": {
"wallet_provider": "WALLET_CODE",
"bank_code": "BANK_CODE"
}
}

Missing or empty required deposit fields return 400. The v2 error envelope contains the numeric HTTP code and a message. Create responses and status lookups follow their own schemas.

For withdrawals, send the recipient identifier in the top-level account_number. You can supply either optional field independently. The v1 payout example shows the same two fields in paymentData.

The common v2 protocol also accepts the customer IP as fields.merchant_user_ip when available. Leave it out if unknown. For v1 PayIn, the same two routing codes go in paymentData.