Feature/dtpayetwo 759 hw parity paypal account dev

[akswaminathan-pp-dev]

JIRA Ticket: DTPAYETWO-759

JIRA Tickets:

• Dev: DTPAYETWO-592
• UT/IT: DTPAYETWO-593

---

Overview

The Design Documentation can be found here: HW Parity with Masspay (REST API)

Currently when creating External Accounts (EA) such as PayPal & Venmo through the REST API method, account numbers were specified to be the following:

EA Type	Account Number Type
PayPal	Email
Venmo	Phone Number

This has now been changed to support the following:

EA Type	Account Number Type
PayPal	Email, Phone Number, PayPal PayerID
Venmo	Email, Phone Number, Venmo Handle, Venmo External ID

With this change, there is a new option to use the "accountId" key-value pair in the HTTP POST Request Body. When GETting an EA, the response body will show this "accountId" value as well. Users are still able to use the "email" key-value if they wish to as well.

OLD:
{
    "type": "PAYPAL_ACCOUNT",
    "transferMethodCountry": "US",
    "transferMethodCurrency": "USD",
    "email": "user@domain.com"
}

------------------------------------------------

NEW:
{
    "type": "PAYPAL_ACCOUNT",
    "transferMethodCountry": "US",
    "transferMethodCurrency": "USD",
    "accountId": "user@domain.com"
}

Added new wallet attribute USE_EMAIL_TAG_FOR_PAYPAL_EA_REST_API.

• If this is enabled for a merchant then they will continue using 'email' in API request & response representation will also have 'email'.
• If this is disabled for a merchant then they will be using 'accountId' in API request & response representation will also have 'accountId'.

Hence we have added a generic error 'email/accountId is required' to accomodate both based on wallet attribute USE_EMAIL_TAG_FOR_PAYPAL_EA_REST_API. Moving forward all merchants will start using accountId.

[coveralls]

Coverage remained the same at 99.287% when pulling 7a97915 on feature/DTPAYETWO-759-HWParity_PaypalAccountDev into 389b782 on master.

[grmeyer-hw-dev]

LGTM