Payment Gateways

Return to Enterprise Driver

• • • Passthru to NF: Sends payment information directly to netFORUM.
    • eWeb Checkout: Sends user using SSO to eWeb for handling payment.
    • Mijireh settings:
      • Mijireh API Key: Optional if using the Mijireh hosted checkout.
    • Payflow settings: Optional if using Payflow hosted checkout.
      • Payflow Mode: Select Test Mode or Live Mode.
      • Payflow Partner: Usually “PayPal”.
      • Payflow Merchant: Fill in the value used at https://manager.paypal.com.
      • Payflow User: Usually same as Merchant.
      • Payflow Password: Fill in the value used at https://manager.paypal.com.
    • Sage settings:
      • Sage Application ID: Must match an application within Sage
      • Sage Merchant ID
      • Sage Merchant Key
  • • Sage JS settings: Uses Sage JS library with their provided widget.
      • Sage Application ID: Must match an application within Sage
      • Sage Merchant ID
      • Sage Merchant Key
      • Sage Developer ID
      • Sage Developer Key
      • SageJS Environment: Either CERT (for certification environment) or PROD (when live).

• • • Vantiv PayPage Iframe: Uses iframe directly from Vantiv so all credit card data lives within vantiv.
    • Vantiv PayPage JS: Uses ajax to retrieve a pre-auth token and credit card number is masked.
    • Vantiv PayPage settings: Please refer to Vantiv JS Documentation for correct credentials.
      • Vantiv PayPage Domain
      • Vantiv LitleXML Communicate Url: Url to communicate with during prelive/live/postlive. (i.e. payments.vantivprelive.com/vap/communicator/online)
      • Vantiv LitleXML Merchant
      • Vantiv LitleXML User
      • Vantiv LitleXML Password
      • Vantiv Report Group