Payment Gateways (Administration)

The Payment Gateways page gives an overview of online payment accounts set through a payment gateway.

Contents:

An online payment gateway is the path between the software, your merchant account, and the card issuers that allows for authorization of credit card payments and settlement of funds to your account. Currently, FBO One supports the MSTS payment gateway only. Internationally, processing is available for Avcard and AIR Card. 

Payment Gateways and Accounts require set up by FBO One support, contact support@amsterdamsoftware.com for any queries.

For more information on Payment Gateways and online payments, see Online Avcard and AIR Card Payments (International Merchants) and Online Credit Card Payments (U.S. Merchants).

Payment Gateways

Columns

Fields

  • Class name: Free text field for the .net class name for the payment gateway logic. If changed contact support@amsterdamsoftware.com.

  • Payment gateway product group: Drop down of available product mapping groups to assign to the payment gateway. See Product Code Mapping for Online Credit Card Payments.

  • First workflow state for new online payments: Drop down of available Online payment workflows. Defines the workflow state an online payment is created with. Default = AHT | New

  • Initialized workflow state: Drop down of available Online payment workflows. Defines the workflow state an online payment uses when the payment gateway is initialized. Default = AHT | Initialized

  • User is redirected to swipe card: Drop down of available Online payment workflows. Defines the workflow state an online payment takes when redirected to the payment gateway to swipe/enter card details. Default = AHT | Redirected to payment gateway

  • Redirected back from payment gateway: Drop down of available Online payment workflows. Defines the workflow state an online payment uses when the user is redirected from the payment gateway. Default = AHT | Gateway result captured

  • Card type is supported and form of payment is set: Drop down of available Online payment workflows. Defines the workflow state an online payment takes when the card type is accepted and payment is ready for authorization. Default = AHT | Ready for authorization

  • Authorize request is send to the gateway: Drop down of available Online payment workflows. Defines the workflow state an online payment takes when payment authorization has been requested to the payment gateway. Default = AHT | Authorization requested

  • Response of authorization request is successful: Drop down of available Online payment workflows. Defines the workflow state an online payment uses when payment has been authorized successfully by the payment gateway. Default = AHT | Authorized

  • Gateway has settled the authorized payment: Drop down of available Online payment workflows. Defines the workflow state an online payment uses when authorized payments are settled by the payment gateway. Default = AHT | BatchSettled

  • Aborted workflow state: Drop down of available Online payment workflows. Defines the workflow state an online payment takes when an online payment has been cancelled. Default = AHT | Aborted

  • Authorization request is declined by gateway: Drop down of available Online payment workflows. Defines the workflow state an online payment takes when payment authorization is declined by the payment gateway. Default = AHT | Authorization declined

Accounts

Columns

  • Name: The name of the payment gateway.

  • Is active: Defines if the payment gateway is active.

  • In test mode: Defines if the payment gateway is in test mode against a test account.

  • Daily settle time UTC: The time that the account payments should be auto settled.

  • Last settle time UTC: The last date and time in UTC and LT the last settle time occurred.

  • Submit batch for settlement: Submit all payments that are not yet batched. If 'Daily settle time UTC' is set, this will automatically happen at the set time.

  • Fetch Cards on File: Fetch the status of all cards on file for this payment gateway account, for checking if cards stored are still active and valid. Note: The ‘CardsOnFileStatusRobot’ robot will perform this check every 60 minutes automatically.

  • Fetch forms of payment: Fetch forms of payment available for the payment gateway. After choosing FBO locations, a summary of fetched forms of payment will be shown, available to view in the Forms of payment (Administration) page. Note: This should be done on setup, and if informed of new supported forms of payment by the gateway provider.

  • Gateway settings: The gateway settings and account details, this should be filled out and maintained by FBO One support. Contact support@amsterdamsoftware.com for any queries.

  • Log: Shows the audit log of the payment gateway account, past settle times can also be viewed here.

Fields

  • Name: Free text name of the payment gateway. It is good practice to add the FBO location or FBO location group that the payment gateway applies to.

  • Is active: Checkbox for defining if the account is active. If checked and ‘In test mode = No’ the gateway account is live.

  • In test mode: Checkbox for defining if the account is in test mode. If unchecked and 'Is active = Yes' the gateway account is live.

  • Daily settle time UTC: The daily time in UTC that payments should be sent for settlement with the payment gateway, when left blank no auto settle is triggered. Format = hh:mm

  • AllowSwipe: Checkbox for defining if the ‘Swipe’ order payment option is available for swipe/entering card details to the payment gateway. If unchecked Pay by email and Card on File by email is still available for online payments.

  • Allow pay by email: Checkbox for defining if 'Pay by email' order payment option is available for sending payment requests by email to customers. See Pay by email & Card on file requests.

  • Allow card on file by email: Checkbox for defining if the 'Card on file request' payment option is available for sending card on file requests by email to customers. See Pay by email & Card on file requests.

  • Portal method note: Free text defining the text shown under payment method for ‘Pay by email’ and ‘Card on file requests’. See Pay by email & Card on file requests.

AHT alliance profiles

Columns/Fields

  • Profile id: Free text the ID of the AHT alliance profile.

  • Profile name: Free text name of the AHT alliance profile.

  • Transacton type: Free text transaction type of the profile, for example COMM or CORP.

  • Product:

  • CardTypeID:

  • MerchantCFType:

  • FDM:

  • LastUpdateDate:

  • Active: Checkbox defining if the profile is active.

  • Log: