added

New Recipient Object Field for Payment Gateway API

In line with BSP and AMLC’s regulatory requirement to monitor funding transactions, Maya will be releasing changes to the Payment Gateway API by April 27, 2023 that will affect merchants under the categories below:

  • MCC 6540: POI (Point of Interaction) Funding Transactions (Excluding MoneySend)
  • MCC 4829: Wire Transf er 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 API change will introduce a new object for recipient details. This will be required for merchants categorized under MCC’s 6540, 4829, and 6538 by May 19, 2023.  
  • This recipient object must contain the details of the receiver for the transaction.
SchemaDescriptionSample Values
$.recipientCONDITIONALObject.
$.recipient.firstNameREQUIRED string, Length: 1-64John
$.recipient.lastNameREQUIRED string, Length: 1-64Doe
$.recipient.accountNumberREQUIRED string, Length: 1-128Value of accountNumber will depend on the accountNumberType. See separate table below.
$.recipient.accountNumberTypeREQUIREDenum. Possible Value

- OTHER
- ROUTING_TRANSIT_NUMBER_AND_BANK_ACCOUNT
- INTERNATIONAL_BANK_ACCOUNT_NUMBER
- CARD_ACCOUNT
- EMAIL
- PHONE_NUMBER
- BANK_ACCOUNT_NUMBER
- WALLET_ID
- SOCIAL_NETWORK_ID
$.recipient.accountTargetIdentificationCodeCONDITIONALstring, maximum of 128 characters

If accountNumberType = BANK_ACCOUNT_NUMBER , this field must be supplied with the target bank’s identification code or BIC
BNORPHMM
$.recipient.addressREQUIRED object
$.recipient.address.line1OPTIONAL string, maximum of 64 characters
$.recipient.address.line2OPTIONAL string, maximum of 64 characters
$.recipient.address.cityOPTIONAL string, maximum of 64 characters
$.recipient.address.stateOPTIONAL string, maximum of 64 characters
$.recipient.address.zipCodeOPTIONAL string, maximum of 10 characters
$.recipient.address.countryCodeREQUIRED string, minimum and maximum length of 3 characters, must be a valid alpha-3 country code

Sample values for Account Number Type

Account Number TypeSample Value
ROUTING_TRANSIT_NUMBER_AND_BANK_ACCOUNT020123456789
INTERNATIONAL_BANK_ACCOUNT_NUMBERGB33BUKB20201555555555
CARD_ACCOUNT5457210001000019
EMAIL[email protected]
PHONE_NUMBER639170123456
BANK_ACCOUNT_NUMBER01234567890
WALLET_ID01234567890
SOCIAL_NETWORK_IDsome_social_network_ID_1234567890
OTHER

Sample

{
  ...,
  "recipient": {
    "firstName": "Maya",
    "lastName": "Juan",
    "accountNumber": "1234567890",
    "accountNumberType": "CARD_ACCOUNT",
    "address": {
      "line1": "6F Launchpad",
      "line2": "Sheridan Street corner Reliance Street",
      "city": "Mandaluyong",
      "countryCode": "PH",
      "state": "Metro Manila",
      "zipCode": "1550"
    }
  }
}

Response Body

The HTTP response body of the APIs will return the recipient object and will apply masking rules on the accountNumber field depending on the accountNumberType.

accountNumberTypeMasking rule on accountNumber
CARD_ACCOUNTShow first 6 and last 4 characters
SOCIAL_NETWORK_IDShow last 4 characters
BANK_ACCOUNT_NUMBERShow last 4 characters
WALLET_IDShow last 4 characters
INTERNATIONAL_BANK_ACCOUNT_NUMBERShow last 4 characters
ROUTING_TRANSIT_NUMBER_AND_BANK_ACCOUNTShow last 4 characters
PHONE_NUMBERShow first 5 and last 3 characters
EMAILShow first 1 and last 10 characters
OTHERShow last 4 characters

Sample Response body and Webhook Data

{
  ...,
  "recipient": {
    "firstName": "Maya",
    "lastName": "Juan",
    "accountNumberType": "BANK_ACCOUNT_NUMBER",
    "accountNumber": "*******7890",
    "accountTargetIdentificationCode": "BOPIPHMM",
    "address": {
      "line1": "6F Launchpad",
      "line2": "Sheridan Street corner Reliance Street",
      "city": "Mandaluyong City",
      "countryCode": "PH",
      "state": "Metro Manila",
      "zipCode": "1550"
    }
  }
}

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 to implement the above-mentioned change the soonest possible as this will become a strict requirement by May 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.