Fortis gateway guide
Adding a Fortis gateway
To add a Fortis gateway:
curl https://core.spreedly.com/v1/gateways.xml \
-u 'C7cRfNJGODKh4Iu5Ox3PToKjniY:4UIuWybmdythfNGPqAqyQnYha6s451ri0fYAo4p3drZUi7q2Jf4b7HKg8etDtoKJ' \
-H 'Content-Type: application/xml' \
-d '<gateway>
<gateway_type>fortis</gateway_type>
<user_id>user_id</user_id>
<user_api_key>user_api_key</user_api_key>
<location_id>location_id</location_id> <!-- optional -->
</gateway>'
<gateway>
<token>4S4RCW9XNB802T0KDPNS9M6RKW</token>
<gateway_type>fortis</gateway_type>
<name>Fortis</name>
<description nil="true"/>
<merchant_profile_key nil="true"/>
<sub_merchant_key nil="true"/>
<user_id>11ef69fdc8fd8db2b07213de</user_id>
<location_id>11ef69fdc684ae30b436c55b</location_id>
<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">true</supports_general_credit>
<supports_void type="boolean">true</supports_void>
<supports_adjust type="boolean">false</supports_adjust>
<supports_verify type="boolean">false</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_offsite_synchronous_purchase type="boolean">false</supports_offsite_synchronous_purchase>
<supports_offsite_synchronous_authorize type="boolean">false</supports_offsite_synchronous_authorize>
<supports_3dsecure_purchase type="boolean">false</supports_3dsecure_purchase>
<supports_3dsecure_authorize type="boolean">false</supports_3dsecure_authorize>
<supports_3dsecure_2_mpi_purchase type="boolean">false</supports_3dsecure_2_mpi_purchase>
<supports_3dsecure_2_mpi_authorize type="boolean">false</supports_3dsecure_2_mpi_authorize>
<supports_store type="boolean">true</supports_store>
<supports_remove type="boolean">true</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_inquire_by_gateway_transaction_id type="boolean">false</supports_inquire_by_gateway_transaction_id>
<supports_inquire_by_order_id type="boolean">false</supports_inquire_by_order_id>
<supports_transaction_retry type="boolean">false</supports_transaction_retry>
<supports_stored_stored_credentials type="boolean">false</supports_stored_stored_credentials>
</characteristics>
<credentials>
<credential>
<name>user_id</name>
<value>11ef69fdc8fd8db2b07213de</value>
</credential>
<credential>
<name>location_id</name>
<value>11ef69fdc684ae30b436c55b</value>
</credential>
</credentials>
<gateway_settings>
</gateway_settings>
<gateway_specific_fields>
<gateway_specific_field>location_id</gateway_specific_field>
</gateway_specific_fields>
<payment_methods>
<payment_method>credit_card</payment_method>
<payment_method>third_party_token</payment_method>
</payment_methods>
<state>retained</state>
<redacted type="boolean">false</redacted>
<sandbox type="boolean">true</sandbox>
<mode>default</mode>
<created_at type="dateTime">2024-12-05T22:06:10Z</created_at>
<updated_at type="dateTime">2024-12-05T22:06:10Z</updated_at>
</gateway>
Note:
The location_id
field is optional to create the gateway and is optional on all transactions except store
; if you plan to use third-party vaulting the location_id
is mandatory.
At Fortis, a gateway profile is referred to as a Location, and each profile has a unique Location ID. The Location ID is used in several transaction request types and is variable per merchant. We recommend making this a configuration variable along with User ID and API Key. A merchant can find these API credentials in their Fortis portal.
Gateway specific fields
Spreedly supports the following gateway specific fields when transacting with Fortis:
location_id
Updated about 1 month ago