Redsys Rest gateway guide
Adding a Redsys Rest gateway
To add a Redsys Rest gateway:
curl https://core.spreedly.com/v1/gateways.xml \
-u 'C7cRfNJGODKh4Iu5Ox3PToKjniY:4UIuWybmdythfNGPqAqyQnYha6s451ri0fYAo4p3drZUi7q2Jf4b7HKg8etDtoKJ' \
-H 'Content-Type: application/xml' \
-d '<gateway>
<gateway_type>redsys_rest</gateway_type>
<login>login</login>
<terminal>terminal</terminal>
<secret_key>secretkey</secret_key>
<account>account</account>
</gateway>'
<gateway>
<token>W5J8YiU1Rtl9HnHT8TYOQlJtbVT</token>
<gateway_type>redsys_rest</gateway_type>
<name>Redsys Rest</name>
<description nil="true"/>
<merchant_profile_key nil="true"/>
<merchant_id>merchantid</merchant_id>
<terminal>terminal</terminal>
<signature_algorithm nil="true"/>
<characteristics>
<supports_purchase type="boolean">true</supports_purchase>
<supports_authorize type="boolean">true</supports_authorize>
<supports_capture type="boolean">true</supports_capture>
<supports_credit type="boolean">true</supports_credit>
<supports_general_credit type="boolean">false</supports_general_credit>
<supports_void type="boolean">true</supports_void>
<supports_adjust type="boolean">false</supports_adjust>
<supports_verify type="boolean">true</supports_verify>
<supports_reference_purchase type="boolean">false</supports_reference_purchase>
<supports_purchase_via_preauthorization type="boolean">false</supports_purchase_via_preauthorization>
<supports_offsite_purchase type="boolean">false</supports_offsite_purchase>
<supports_offsite_authorize type="boolean">false</supports_offsite_authorize>
<supports_3dsecure_purchase type="boolean">true</supports_3dsecure_purchase>
<supports_3dsecure_authorize type="boolean">true</supports_3dsecure_authorize>
<supports_3dsecure_2_mpi_purchase type="boolean">true</supports_3dsecure_2_mpi_purchase>
<supports_3dsecure_2_mpi_authorize type="boolean">true</supports_3dsecure_2_mpi_authorize>
<supports_store type="boolean">false</supports_store>
<supports_remove type="boolean">false</supports_remove>
<supports_fraud_review type="boolean">false</supports_fraud_review>
<supports_network_tokenization type="boolean">false</supports_network_tokenization>
<supports_populate_mit_fields type="boolean">false</supports_populate_mit_fields>
<supports_3dsecure_2_purchase type="boolean">true</supports_3dsecure_2_purchase>
<supports_3dsecure_2_authorize type="boolean">true</supports_3dsecure_2_authorize>
</characteristics>
<credentials>
<credential>
<name>merchant_id</name>
<value>merchantid</value>
</credential>
<credential>
<name>terminal</name>
<value>terminal</value>
</credential>
<credential>
<name>signature_algorithm</name>
<value nil="true"/>
</credential>
</credentials>
<gateway_settings>
</gateway_settings>
<gateway_specific_fields>
<gateway_specific_field>user_agent</gateway_specific_field>
<gateway_specific_field>accept_header</gateway_specific_field>
<gateway_specific_field>authentication_method</gateway_specific_field>
<gateway_specific_field>authentication_type</gateway_specific_field>
<gateway_specific_field>authentication_flow</gateway_specific_field>
<gateway_specific_field>sca_exemption</gateway_specific_field>
<gateway_specific_field>use_webservice_endpoint</gateway_specific_field>
</gateway_specific_fields>
<payment_methods>
<payment_method>credit_card</payment_method>
</payment_methods>
<state>retained</state>
<redacted type="boolean">false</redacted>
<sandbox type="boolean">false</sandbox>
<created_at type="dateTime">2021-08-31T19:25:45Z</created_at>
<updated_at type="dateTime">2021-08-31T19:25:45Z</updated_at>
</gateway>
3DS exemptions
Redsys Rest has systems in place to ensure that correct transaction types and exemption scenarios are flagged. However, there are some circumstances where particular values need to be sent to three_ds_exemption_type
, as outlined below:
Spreedly value | Redsys value |
---|---|
corporate_card | COR |
delegated_authentication | ATD |
low_risk | TRA |
low_value | LWV |
trusted_merchant | NDF |
Updated about 1 month ago