New Recipient Object Field For Payments Processing Platform
In line with BSP and AMLC’s regulatory requirement to monitor funding transactions, Maya will be releasing Payments Processing Platform API v1.3.7 by March 30, 2023 that will affect merchants under the categories below:
- MCC 6540: POI (Point of Interaction) Funding Transactions (Excluding MoneySend)
- MCC 4829: Wire Transfer Money Orders (V, D, G, X) Money Transfer (M)
- MCC 6538: MoneySend Funding
This regulatory requirement aims to ensure that acquirers are sending complete, verified, and accurate information to assist receiving issuers in their authorization decisions and regulatory obligations. To implement these required API changes, kindly advise your developers, IT teams, and/or tech teams on this activity.
What are the API changes?
- The new API version will introduce a new object for
recipientdetails undertransaction. This will be required for merchants categorized under MCC’s 6540, 4829, and 6538 by April 19, 2023. - This
recipientobject must contain the details of the receiver for the transaction.
| Schema | Description | Sample Values |
|---|---|---|
$.transaction.recipient | CONDITIONALObject. | |
$.transaction.recipient.firstName | REQUIRED string | John |
$.transaction.recipient.lastName | REQUIRED string | Doe |
$.transaction.recipient.accountNumberType | REQUIRED enum. Possible Values- OTHER - ROUTING_TRANSIT_NUMBER_AND_BANK_ACCOUNT - INTERNATIONAL_BANK_ACCOUNT_NUMBER - CARD_ACCOUNT - PHONE_NUMBER - BANK_ACCOUNT_NUMBER - WALLET_ID - SOCIAL_NETWORK_ID | |
$.transaction.recipient.accountNumber | REQUIRED string, maximum of 128 characters | Value of accountNumber will depend on the accountNumberType. See separate table below. |
$.transaction.recipient.accountTargetIdentificationCode | CONDITIONALstring, maximum of 128 charactersIf accountNumberType = BANK_ACCOUNT_NUMBER , this field must be supplied with the target bank’s identification code or BIC | BNORPHMM |
$.transaction.recipient.address | REQUIRED object | |
$.transaction.recipient.address.line1 | OPTIONAL string, maximum of 64 characters | |
$.transaction.recipient.address.city | OPTIONAL string, maximum of 64 characters | |
$.transaction.recipient.address.state | OPTIONAL string, maximum of 64 characters | |
$.transaction.recipient.address.postalCode | OPTIONAL string, maximum of 10 characters | |
$.transaction.recipient.address.alphaCountryCode | REQUIRED string, minimum and maximum length of 3 characters, must be a valid alpha-3 country code | |
Sample values for Account Number Type
| Account Number Type | Sample Value |
|---|---|
| ROUTING_TRANSIT_NUMBER_AND_BANK_ACCOUNT | 020123456789 |
| INTERNATIONAL_BANK_ACCOUNT_NUMBER | GB33BUKB20201555555555 |
| CARD_ACCOUNT | 5457210001000019 |
| [email protected] | |
| PHONE_NUMBER | 639170123456 |
| BANK_ACCOUNT_NUMBER | 01234567890 |
| WALLET_ID | 01234567890 |
| SOCIAL_NETWORK_ID | some_social_network_ID_1234567890 |
| OTHER |
Sample
{
...,
"transaction": {
...,
"recipient": {
"firstName": "John",
"lastName": "Doe",
"address": {
"line1": "Line 1",
"city": "Mandaluyong",
"state": "Metro Manila",
"postalCode": "1550",
"alphaCountryCode": "PHL"
},
"accountNumber": "[email protected]",
"accountNumberType": "EMAIL"
}
},
}
What are the steps to implement this change?
The recipient object should be included in the JSON input when calling the following API endpoints:
To ensure compliance, we highly recommend implementing the above-mentioned change the soonest possible as this will become a strict requirement by April 19, 2023.
Who will be affected?
Merchants who are categorized under MCC 6540, 4829 and 6538.
Need help?
For any questions or concerns, please contact us through our support channels.