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.
| Operation | JSON field | Type | Required | Meaning |
|---|---|---|---|---|
| Deposit | fields.wallet_provider | string | Yes | Wallet provider code enabled for the shop. |
| Deposit | fields.bank_code | string | Yes | Bank code supplied for the selected shop. |
| Withdrawal | fields.bank_code | string | Optional | Code for the recipient's bank. |
| Withdrawal | fields.holder | string | Optional | Name 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.