Consumer Identity Mapping

[tblachowicz]

In section Conumer Identity there is a list of three parameters related to requested details of the consumer. They map nicely to equivalent parameters specified in PaymentOptions dictionary of PR API.

I'd like to consider adding the following mapping between PR API PaymentOptions and SRC DpaTransactionOptions to the definition of payment method:

• requestPayerName maps to consumerNameRequested
• requestPayerEmail maps to consumerEmailAddressRequested
• requestPayerPhone maps to consumerPhoneNumberRequested

The question remains open whether the requested/required details should be included in the encrypted payload as per SRC specification or in PayerResponse.