July 2022 Release Notes
New Merchant Signup Form available in the Portal - UI and UX Improvements.
Issue resolved where required documents on signup forms would not display the label of the type of document, next to the uploaded form. This helps to prevent duplicate uploads of the same required documents from the customer.
Issue resolved where pre-populating a custom field in the signup form where hidden fields would display the whole URL as opposed to the specified field. This helps to prevent issues with data formatting, allowing clients to map merchants with custom IDs.
Issue resolved where some fields would not load on the signup form if the website option is toggled on or off.
Issue resolved where pre-population of signup form data would not track from a custom URL like the previous version.
Issue resolved where URLs created in the Signup Form page or settings would not display in the live production signup form.
New requirement (red) asterisks have been added to the “Filter By” option to note that the field (and its specific selections) is required and help to avoid confusion around the parameters required for Transaction Details Reports and Profit and Loss Reports.
Profit and Loss (P&L) Report Query has been updated to ensure all merchants are included for unique use cases.
Issue resolved where customer’s name would not display in the Disbursement Transaction Details report.
Issue resolved where the boarding status shown in Merchant Results Reports would falsely display a “Successfully Boarded” status when the Merchant application was still in a “Manually Review” or “Not Boarded Yet” status.
Two additional terminal types have been added to the Portal: Datacap E-Pay & Freedom Pay
All Risk Credentials have been restricted to the Premium Partner Admin role resource only within the Portal.
The following fields have been added to the Portal Add Merchant form:
Annual Processing Volume (required)
Average Transaction Amount (required)
Middle Name (optional)
Portal now displays an error message if a terminal VAR sheet is no downloaded successfully for the user: “VAR sheet could not be downloaded.”.
Portal now displays a success message for successfully processed eCheck transactions: “Successfully Submitted.”.
Portal now displays compliance notices on the owners pages to ensure owners meet compliance requirements:
“Please Note : To help the government fight the funding of terrorism and money laundering activities, federal law requires all financial institutions to obtain, verify, and record information that identifies each individual or business who opens an account. What this means for you: when you open an account, we will ask for your identifiable information including your full name, address, date of birth, and other business information that will allow us to identify you. We may also ask to see your Identification Card, Driver's License, and/or other identifying documents.”
“Please Note: The following information must be provided for Sole Proprietors or each individual, if any, who directly or indirectly owns twenty-five percent (25%) or more of the ownership interest of the Legal Entity in this application as well as an individual with significant responsibility. A Legal Entity includes a general partnership, a corporation, limited liability company or other entity that is formed by a filing of a public document with a Secretary of State or similar office, and any similar business entity formed in the United States.”
Portal now displays a warning message before a user confirms changes on the Settings/Color Themes page:
“Changing the color will impact the whole portal. All users that use the portal will see the new color.”
Issue resolved where parent users logging in to a child user’s Portal would be kicked from the Portal while trying to access Alerts within Transaction Details with a 403 error.
Issue resolved where partner white-label branding would not display the intended partner logo on their client facing URL.
Issue resolved where Referrers logged in as Merchant in the portal would display an incorrect date of birth for the Merchant’s business owner.
Issue resolved where various lightbox headers displayed incorrect title under Add eCheck and Add Terminal.
Issue resolved where canceled eCheck transactions would not reflect in the database, causing an error when attempting to re-process an eCheck transaction.
Two additional terminal types have been added to the API: Datacap E-Pay & Freedom Pay.
Transaction surcharges within the API now automatically send the surchargeAmount endpoint data to Vantiv for compliance.
Jobs now include an
injectTimecron entry parameter to automatically include the current time of the job, preventing duplicates and providing faster visibility into job batches.
Email Alerts have been added to the API to send email notifications for bank account and routing number changes.
DisbusementRefsnow include a create request to process a single disbursement and create multiple
DisbursementRefssplit between the specified entities.
New unique identifier added to merchant
access_tokenendpoint to be stored for later troubleshooting with PLAID integration.
PostProcessorhas been updated to submit payout processing jobs (disbursements) by entity, and a lock has been added to prevent two users under the same entity from submitting a payout job at the same time.
PostProcessorhas been updated and initiate debit processing jobs for entities with negative funds.
Issue resolved where ampersands (&) and other special characters would cause issues while using the Wells Fargo autoboarding feature.
Issue resolved where Partners charging annual fees to multiple merchants using the same annual fee start/collection date would cause a delay to some Merchants’ statement entry being generated.
Issue resolved where payout descriptors (primary and secondary) would not show as intended within the end users’ account statements.
Issue Resolved where editing the credit card number within PayFields would cause the cursor to jump to the end of the text row.
Issue Resolved where disbursements would return as failed from sub-merchants to Partners displaying the failure message: “Invalid sub-merchant”.
Issue resolved where duplicate requests would display multiple duplicates of merchant fields.
Issue Resolved where a batch file of multiple refunds of the same amount would be rejected from Vantiv as duplicates.
Issue resolved where authorized transactions created in sandbox would not consistently create a txnRef in the API response.