Fortis (Zeamster) integration guide

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
  • Card
Supported transaction types
  • Sale (saved card token) ( API )
  • Auth Only (saved card token) ( API )
  • Capture (partial and greater than) ( API )
  • Void ( API )
  • Refund (partial and multiple) ( API )
Supported processing currenciesUSD
3D Secure 1.x supportedNo
3D Secure 2.x supportedNo
External 3D Secure supportedNo
Installments supportedNo

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.

Testing data

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

BrandCard numberExpiration dateSecurity codeCardholder nameAmountTransaction result
Visa4000100011112224Any future dateAnyAnyAnySuccess
Visa4000300011112220Any future dateAnyAnyAnySuccess
VisaAny of the aboveAny future dateAnyAny$6.01Generic decline
VisaAny of the aboveAny future dateAnyAny$6.15Do not honor
VisaAny of the aboveAny future dateAnyAny$6.27System error

Status workflows

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

SaleWhen isAuthOnly is false, successful sale transactions will have the following statuses:
  • pending* or authorized
  • settled
Auth onlyWhen isAuthOnly is true, successful sale transactions will have the following status:
  • authOnly
CaptureSuccessful capture transactions will have the following statuses:
  • pending* or authorized
  • settled
VoidSuccessful void transactions will have the following status:
  • voided
RefundSuccessful refund transactions will have the following statuses:
  • 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.