Skip to main content

Chase E-xact Hosted Payments

UnlikeThe the Direct Post Method,Chase E-xact usesHosted Payment configuration allows administrators to process secure online transactions through the Chase E-xact payment gateway. Its primary purpose is to safely redirect users to a Hosted Payment Page (HPP) during checkout, ensuring sensitive payment data is securely handled outside of OPS-COM before posting the transaction results back to the system. This article is intended for OPS-COM administrators.

Setup and Configuration

To configure the Chase E-xact integration, you must gather specific credentials from your merchant account so they can be entered into the system.

  1. Log in to your Chase E-xact merchant portal.

  2. Retrieve your exact Company Name, your E-xact ID (Gateway ID), and the Password used to access your account.

  3. Hover over System Configuration and click Payments then Setup Payment Types.

  4. Click the Add Type button.

  5. Select the Chase E-xact option from the provider drop-down menu.

  6. Click the Next Step button.

  7. Enter your Company Name, E-xact ID, and Password into the respective credential configuration fields.

  8. Click the Update Payment Type button to save your credentials and activate the gateway.

Using this Feature

Because this integration utilizes a Hosted Payment Page (HPP) with a Relay Response.Response, administrators do not manually interact with this feature on a daily basis. Once configured, the Chase E-xact integration automatically handles electronic routing when users process transactions on the user portal.

The customerstandard isuser checkout flow proceeds as follows:

  1. Select the Chase E-xact payment type during the OPS-COM checkout process.

  2. Click the confirmation button to be securely redirected to E-xact's secureexternal payment form,form.

  3. Enter the required credit card details on the secure HPP.

  4. Confirm the payment details to process the funds.

Visual Cues and Status Indicators

  • Automated Redirection: Once the payment successfully processes, the transaction results are posted back to ourthe OPS-COM webhook endpoint. The user is then automatically redirected back to the OPS-COM portal, where a final payment confirmation screen and receipt are generated for their records.

SettingBest upPractices Chaseand Considerations

  • Maintain Credential Security: Always ensure your merchant account password and E-xact PaymentsID

    Inare orderkept up to configuredate in the clientsystem. OPSCOMIf siteyour password expires or is changed within the external Chase portal, you must immediately update it within your OPS-COM payment settings to useprevent Chasecheckout E-xactfailures.

    Hosted
    • Payments

  • Webhook Verification: Perform a small test transaction before going live to verify that the clientRelay mustResponse supplyis correctly posting the followingresults credentials:

    • Company Name
    • Their exacted
    • The password usedback to accessthe OPS-COM webhook endpoint and properly triggering the accountfinal receipt generation.

Back to top