Contents
- Introduction
- Enable Enhanced Payments Gateway UI
- Payments Gateway Page Structure
- Surcharge Fee Configuration
- Customer-Level Payment Processing Surcharge Settings
- Background Jobs and Progress Indicators
- Audit Logs for Payments Gateway
Introduction
The Enhanced Payments Gateway UI (V2) introduces a cleaner, structured, and more intuitive configuration experience for managing payment gateways, payment methods, and surcharge behavior.
This update improves usability, transparency, and system traceability through structured layouts, contextual settings, surcharge controls, background job indicators, and enhanced logging.
Note
The Enhanced Payments Gateway UI is now enabled by default for:
- Ordway Payments
- Adyen Gateway
- Stripe Gateway
The Enhanced Payments Gateway UI provides:
- Sectioned gateway configuration
- Contextual transaction settings per payment method
- Granular surcharge controls
- Customer-level surcharge visibility
- Background job progress indicators
- Integrated audit and activity logs
Audience
This document is intended for:
- System administrators
- Payment operations teams
- Implementation engineers
- Support and solutions architects
Prerequisites
Before enabling the Enhanced Payment Gateway UI:
- You must have administrator-level access
- At least one payment gateway must already be configured
- You must have permission to update payment and customer settings
Enable the Enhanced Payments Gateway UI
The upgraded experience is controlled by a feature toggle.
- In the left navigation menu, click Setup > Settings. The Company Settings page is displayed.
- Under the Payment section, enable Enhanced User Interface for Payments Gateway toggle.
- Click Save.
- The updated Gateway Model page layout is applied immediately and the “Settings updated successfully” confirmation message appears.
Payments Gateway Page Structure
Navigate to: Setup → Payments Gateway. The page is divided into logical sections to simplify configuration.
Electronic Payments with (Payment Gateway name)
- Use this section to specify or update the Payment Account Name. This configuration is mandatory and must be completed before proceeding to other sections.
Accepted Payment Methods
This section displays all payment methods supported by the selected gateway.
Key Characteristics
- Existing functionality remains unchanged.
- Each payment method can be expanded or collapsed.
- Selecting a payment method activates its corresponding Transaction Settings.
Transaction Settings
Transaction settings are displayed contextually based on the selected payment method.
Example: When ACH Debit is selected:
- ACH-specific settings appear immediately.
- By default, the Enable ACH Debit for all customers check box is enabled.
- You can disable this option at the gateway level and enable this setting at the individual customer level manually.
Surcharge Fee Configuration
The Enable charging customers an additional fee option includes additional controls to define applicability.
Available options
- Enable this setting for all existing customers
- Enable this setting for new customers
After selecting the desired options, you can configure and save the surcharge fee value.
Behavior by Customer Type
| Configuration | Result |
| Surcharge enabled only | Displays surcharge option on Customer Details page (unchecked by default) |
| Enabled for existing customers | Automatically enables surcharges for all existing customers who do not already have it enabled. Existing enabled customers remain unchanged. |
| Enabled for new customers | Automatically enables surcharge for newly created customers |
Advanced Configuration
The Advanced Configuration section provides additional controls for payment behavior, UI visibility, and synchronization with Stripe.
Available Options
The following options are available:
Restrict saved Payment Method(s) from being displayed on UI.
When enabled, saved payment methods will be hidden from the customer-facing payment interface.
What This Does
- Hides previously saved payment methods from:
- Hosted payment pages
- Customer payment screens
- Does not delete saved payment methods.
- Only controls UI visibility.
Tooltip Text: Click here for more information.
Receive Payment Changes Done Directly on Stripe
When enabled, Ordway receives real-time payment updates from Stripe.
This Includes
- Payment status updates
- Refunds
- Chargebacks
- Other Stripe-side changes
These updates are reflected in Ordway automatically.
Tooltip Text: Enabling this allows Ordway to receive real-time updates from Stripe for any payment changes made directly on Stripe.
Requirement: Stripe webhooks must be enabled.
For more information, see Connect and Manage Stripe Gateways in Ordway
Send Email for Payments That Are Triggered from Stripe
This option is available only when Receive payment changes done directly on Stripe are enabled.
When enabled
- Email notifications are sent for payments created or updated directly in Stripe.
- The system uses configured payment email templates.
Important: The customer ID on Stripe should match the Customer Payment Gateway ID in Ordway.
If the IDs do not match, synchronization and email notifications may not work as expected.
Customer-Level Payment Processing Surcharge Settings
When a payment method is enabled in Setup → Payments Gateway, it becomes available for selection on the Customer Details page under Electronic Payment Methods.
With the upgraded Payments Gateway UI, surcharge (processing fee) configuration at the gateway level also controls whether surcharge options appear at the customer level.
How It Works
Electronic Payment Methods (Existing Behavior)
When you select a payment method in:
-
Setup → Payments Gateway → Accepted Payment Methods.
That payment method becomes available on the Customer Details page under:
- Payment Information → Electronic Payment Methods. This behavior remains unchanged.
Surcharge Visibility at Customer Level (New Behavior)
When “Enable charging customers an additional fee” is enabled at the gateway level for a specific payment method, a corresponding surcharge checkbox becomes available on the Customer Details page.
This allows surcharge settings to be controlled per customer — but only if the feature is enabled at the gateway level.
Location
Customers → Select Customer → Payment Information → Payment Processing Fee Options.
Example: If the ACH debit is enabled for processing fee at the gateway, On the customer details page, ACH debit will be enabled.
When Does the Surcharge Checkbox Appear?
A surcharge checkbox appears on the Customer Details page only when:
- The payment method is enabled in Accepted Payment Methods, and
- Processing surcharge is enabled for that payment method at the gateway level.
If surcharge is not enabled at the gateway level, the checkbox does not appear at the customer level.
Background Jobs and Progress Indicators
Some gateway updates trigger background processes. To improve transparency and prevent duplicate submissions, Ordway displays:
- A user-friendly informational message
- A visual progress bar
These indicators inform users that the requested change is being processed.
The following message appears:
- Your request to modify the Gateway Settings is being processed. Please hold on, or you can close the screen and your request will continue processing in the background.
The progress bar visually indicates that processing is in progress. All updates are logged in Audit Logs.
Audit Logs for Payments Gateway
The Audit Logs page provides a complete history of configuration and system changes made within Ordway, including updates to the Payments Gateway.
The system records:
- Audit Logs
- Webhook Logs
- API Logs (where applicable)
These logs provide visibility into gateway configuration updates and payment-related integrations.
Where to Access Logs
- In the left navigation menu, click Setup → Payments Gateway. The Setup Electronic Payment page is displayed.
- Click the three-dot menu next to Manage.
- Click Audit Log. The Audit Logs page is displayed.
Audit Log Columns
The following columns are displayed:
| Column | Description |
| Date | Timestamp of the event (with time zone) |
| User | User who performed the action |
| Event | Description of the action performed |
| Source | Origin of the change (UI, API, etc.) |
Comments
0 comments
Please sign in to leave a comment.