...
| Info |
|---|
IVR ConsiderationsWhen the merchant is using an IVR flow, they must confirm with their account manager that Payer Authentication configuration has the following 2 flags disabled have;
|
Field Name | Description | Required | Field Definition |
|---|---|---|---|
AuthenticationChannel | Indicates the available mediums supported by the device for authentication. Possible Values: IVR - Via Interactive Voice Response | Y | AN(15) |
MobileIdFormat | Designates the format of the MobileId field. Possible Values: D - Domestic I - International Example: D = AAANNNNNNNNNN I = CCCAAANNNNNNNNNN NOTE: C = Country Code, A = Area Code, N = Subscriber Number | Y | A(1) |
MobileId | The phone number or Mobile Id used to authenticate the device. This is the number/id registered with the ACS. | Y | N(25) |
PareqChannel | Indicates how the transaction is being routed between the merchant and the issuing bank during authentication. Possible Values: DIRECT - value indicates to the ACS to communicate directly with the MPI via server to server communication over the internet. | Y | AN(15) |
ShoppingChannel | Indicates how the transaction is being initiated. Possible Values: IVR - Via Interactive Voice Response | O | AN(15) |
TtpCredential | Value sent by the ITP (Issuer Trusted Party) to the issuer in order to prove its relationship. NOTE: This field is only used if the Merchant has an ITP with the ACS. At the time of publication, ITP has not been implemented by any IVR ACS. | O | AN(80) |