The overrides occur individually for example, you could pass in a mit_msg_type of CGEN, but use the default fields for everything else.įor more information on the accepted values for these fields, please see Orbital’s “Stored Credentials Framework” documentation. These fields are mit_msg_type, mit_stored_credential_ind, and mit_submitted_transaction_id. However, we also allow a few gateway specific fields related to Stored Credentials to be specified, which will override the default Stored Credential Data fields. Stored credential gateway specific fieldsĪn Orbital (Chase Paymentech) gateway supports our standardized Stored Credential Data fields. Detailed descriptions and example requests using these 4 key fields can be found in Orbital’s documentation. SCARecurringPayment expects AuthenticationECIInd to have a value of 7. The UCAFInd field is always passed with a value of 4 and also requires the MCProgramProtocol and MCDirectoryTransID fields. Please see Orbital’s third-party 3DS2 documentation for detailed descriptions of each of these fields and when to use them.Īdditionally, Orbital has 4 key fields that are applicable only to Mastercard 3DS2 transactions: UCAFInd, MCProgramProtocol, MCDirectoryTransID, and SCARecurringPayment. Spreedly fields map to the relevant Orbital fields as described in the following table. For more information about how to use this feature, see the 3DS2 Third-party Authentication Guide. Spreedly will automatically handle the field mapping for sending third-party 3DS2 authentication data to Orbital. "merchant_id"=>"Your 3D Secure 2 Auth Data To add an Orbital (Chase Paymentech) gateway using your full set of credentials: Making this deal even worse than before.Adding using Merchant Credentials and Merchant ID mode Also requires opening a chase total business checking account as well.
0 Comments
Leave a Reply. |