AudienceView Connect

ServeBase

To access the ServeBase payment gateway, navigate to the Registry application System::Configuration::Payment Gateways node.

Information
For those gateways that require a file to be passed by ServeBase, add a new 'Key' to the Payment Gateways list in the format of Servebase::yourPathToTheFile. For more information, refer to General Configuration - Lists.
Field Description
3DSResult_URL The URL of ServeBase's 3D Secure results gateway, specifically https://testing1.servebase.com/WX23DSecure/Get3DSResult.asp.
3DSecure_enabled Determines whether the payment gateway will use 3D Secure:
  • Yes: 3D Secure will be enabled.
  • No: 3D Secure is not enabled.
AVS_Error_Number Address verification error used by Servebase.
CSC_AVS_Override 0: The CVV and AVS are not required.
1: Fail the transaction on an address verification failure.
2: Fail the transaction on a CVV failure.
3: Fail the transaction in the event that either the AVS check or the CVV check fails.
4: Override the default behaviour and process the transaction on either AVS or CVV failures.
CSC_And_AVS_Error_Number Address and CVV verification error used by Servebase.
CSC_Error_Number CVV verification error used by Servebase.
Host_URL The URL of ServeBase's gateway, specifically https://testing1.servebase.com/WX23DSecure/srv_vbv_post.asp.
PIN Pad timeout
(As of AudienceView 6.8.8)
This parameter sets the value for the socket receive timeout if a PIN pad is used.
This is set to 120 (seconds), by default.
Verify_URL The URL of ServeBase's verificaiton gateway, specifically https://testing1.servebase.com/WX23DSecure/bespoke/AVVerify.asp.
acquirer This is a three chartacter bank brand from the merchant provider (e.g. AIB or NWB) and is used when 3D Secure is enabled for an Internet transaction.
hostname Name or IP of the computer running the Servebase software (PC-EFT).
hostport Port number of the computer running the Servebase software (PC-EFT).
library_path Absolute path to respective AudienceView payment gateway DLL
log_file Absolute path to a file on the local server where payment processing data is saved. Include the file name in the path. If the file does not exist, it will automatically be created.
process_details For those gateways that support multiple types of payments, this field identifies the type of payment (e.g. Credit or Debit).
process_strategy Identifies how the payment is to be processed:
  • External: Process payment external third party.
    This is the only valid option for this payment gateway.
  • Account: Process payments as an AudienceView internal account.
  • Gift Card: Process payment as an AudienceView gift certificate.
  • Gift Certificate: Process payment as an AudienceView gift certificate.
rotate_log_file Y: a new log file will be created each day, with the creation date included as part of its name. 
N: a single log file is used.
It is recommended that you use log rotation, as the log file is locked while the application is running and cannot be moved or deleted.
security_capabilities Identifies how the payment will be processed with security:
  • MasterCard SecureCode: Security offered through MasterCard.
  • SecureCode and VbV: Using SecureCode and VbV (Verified by Visa).
  • Verified by Visa: Using Verified by Visa only.
terminal_allocation Queued: Requires AudienceView to queue the requests to the terminals.
Round Robin: Gateway can queue the requests on its terminals.
terminal_required Swiped: Only requires a terminal for swiped transactions using the pinpad.
For more information on configuring terminals, refer to Terminals and Configuring Payment Terminals.
timeout TCP/IP timeout, in seconds.
verbose_log Y: log file contains detailed information. 
N: log file contains summary information.