Closed ianbjacobs closed 5 years ago
From 15 May discussion, this parameter would not be a filtering param but more for tailoring response data or backend behavior based on transaction type.
From 29 May discussion [1] the conclusion is that this parameter is useful. We plan to update the payment method definition with information from the SRC specification when it is made publicly available.
In SRC 1.0, I see that Transaction Types are defined in "Recommendations for EMV Processing for Industry-Specific Transaction Types" [1], but that document is labeled as being for "Contact" transactions and is from 2016. I will ask the task force for clarification.
At the 12 June task force call [1] we resolved to include an optional transactionType parameter that refers to the EMVCO API spec for authoritative information, but includes 5 values inline for convenience. The rationale for inclusion is that the response or backend behavior may change based on this information.
Do we need a request parameter for transactionType? (e.g., Purchase, P2P).