Fortis (Zeamster) Fortis (Zeamster) is a gateway that allows you to collect card payments. This guide is intended to help you implement Fortis (Zeamster) based on your preferred integration workflow.

Services and compatibility


Supported payment types	<ul style={{ marginTop: "-5px", marginBottom: "-5px" }}> Card
Supported transaction types	<ul style={{ marginTop: "-5px", marginBottom: "-5px" }}> Sale (saved card token) ( API / API with iframe / Tutorial ) Auth Only (saved card token) ( API / Tutorial ) Capture (partial and greater than) ( API / Dashboard ) Void ( API / Dashboard ) Refund (partial and multiple) ( API / Dashboard )
Supported processing currencies	USD
3D Secure 1.x supported	No
3D Secure 2.x supported	No
External 3D Secure supported	No
Installments supported	No

Gateway-specific information

Fortis (Zeamster) does not settle batches immediately.
paymentType is not supported.

Configuration

Work with Integrations Support to add Fortis (Zeamster) as a connection. You will need the following credentials from Fortis (Zeamster):

user ID
user API key
product transaction ID

Required fields

There are no additional required fields.

If you are having issues with transactions that are rejected by Fortis (Zeamster) because of potential fraud, include the clientIp parameter in the payment request and explicitly set the value as the IP address of the device where the customer is submitting the payment information. If you do not explicitly set a value, it looks to Fortis (Zeamster) as if the exact same IP address is sending out an inordinate amount of traffic and it is not possible to separate out the valid and invalid requests.

Testing data

Use the following test card information to test your Fortis (Zeamster) configuration.

Brand	Card number	Expiration date	Security code	Cardholder name	Amount	Transaction result
Visa	4000100011112224	Any future date	Any	Any	Any	Success
Visa	4000300011112220	Any future date	Any	Any	Any	Success
Visa	Any of the above	Any future date	Any	Any	$6.01	Generic decline
Visa	Any of the above	Any future date	Any	Any	$6.15	Do not honor
Visa	Any of the above	Any future date	Any	Any	$6.27	System error

Status workflows

The status of a successful transaction with Fortis (Zeamster) varies, depending on the options you choose.


Sale	When `isAuthOnly` is `false`, successful sale transactions will have the following statuses:<ul style={{ marginTop: "-5px", marginBottom: "-5px" }}> pending* or authorized settled
Auth only	When `isAuthOnly` is `true`, successful sale transactions will have the following status: <ul style={{ marginTop: "-5px", marginBottom: "-5px" }}> authOnly
Capture	Successful capture transactions will have the following statuses:<ul style={{ marginTop: "-5px", marginBottom: "-5px" }}> pending* or authorized settled
Void	Successful void transactions will have the following status:<ul style={{ marginTop: "-5px", marginBottom: "-5px" }}> voided
Refund	Successful refund transactions will have the following statuses:<ul style={{ marginTop: "-5px", marginBottom: "-5px" }}> pending* or authorized settled

*Pending status displays as "authorized" or "AUTHORIZED" in the Nexio Dashboard; it displays as 10, meaning "authorized", in the response when querying transactions (for more information about transactionStatus, see the appropriate transactionStatus table).

If you have any additional questions or feedback, contact us.

Fortis (Zeamster) integration guide