Onboarding Improvements
We've resolved three critical issues that were blocking or complicating the merchant onboarding process.
Fixed: Multi-Store Application Error
The Problem Merchants were unable to submit applications for accounts with two or more store locations. The form would reject the submission with a validation error, causing delays and frustration.
What We Fixed This validation error has been resolved. Multi-store applications now submit successfully on the first attempt.
Impact for Your Merchants Your merchants with multiple store locations can now complete their onboarding without workarounds or support tickets.
Fixed: Fiserv Application Submission Error
The Problem When submitting a Fiserv merchant application, the form incorrectly flagged the ACH Disbursement Method as missing—even when the field was properly completed. This blocked otherwise complete applications from being submitted.
What We Fixed The form validation logic has been corrected. The ACH Disbursement Method field no longer generates false errors.
Impact for Your Merchants Fiserv applications now process without hitting this validation blocker, reducing support escalations and onboarding delays.
Fixed: Missing Merchant Admin Access
The Problem When a partner's display name differed from their Adyen ID, merchant admin accounts created during onboarding approval were missing their assigned Partner, Company, and Location access. This left admins unable to fully manage their accounts.
What We Fixed Admin access assignment now works correctly regardless of name variations between your display name and Adyen ID.
Impact for Your Operations Your merchant admins will have the correct permissions and account access from day one, eliminating post-onboarding access correction requests.
Reporting & Data Accuracy Improvements
Fixed: Transaction Date Grouping
The Problem On the Deposit Details page, transactions were appearing under incorrect date group headers. A transaction authorized on an earlier date but settled in a later deposit would display under the wrong date, creating confusion during reconciliation.
What We Fixed Transactions are now grouped by their settlement date, matching both the Settlement Date column and the actual deposit date. This ensures accurate organization of transaction data.
Impact for Your Merchants Merchants can now accurately reconcile deposits without confusion about why transactions appear where they do. This reduces support inquiries about deposit timing and transaction placement.
Improved: ACH Return Reason Details
The Problem When an ACH payment failed, the dispute action banner always displayed a generic "insufficient funds" message—even when the actual return reason was different. This made it difficult for merchants to understand why a payment was rejected.
What We Fixed The dispute banner now displays the actual reason for the ACH return, not a generic placeholder.
Impact for Your Merchants Your merchants can now see the specific reason their ACH payment was returned (insufficient funds, account closed, invalid account, etc.), helping them troubleshoot quickly without contacting support.
User Experience Improvements
Improved: Date Range Picker
What Changed The date picker on the Dashboard, Payments, and Deposits pages has been redesigned. Instead of managing two separate calendars, partners now select a start date and end date on a single unified calendar. The entire selected range highlights for easy visualization.
Why This Matters Faster report generation with less navigation. Partners can see their full date range at a glance and submit queries more quickly.
Improved: Terminal Configuration Error Messaging
What Changed When a merchant's stores are not configured for Adyen terminals, the portal now displays a specific, actionable error message instead of a generic error code.
Why This Matters Your merchants understand what's wrong and what they need to do next, reducing support tickets and enabling faster resolution.