‍

Streamlining card dispute management with our new Disputes API and an improved Console experience

We launched a brand new Disputes API and an improved Console experience to make it easier to submit and manage card disputes.

Through the Disputes API, your end users can now create new disputes, upload supporting documentation, and update disputes directly through your platform, improving your end-user experience and increasing operational efficiencies. A Dispute Case in the Synctera Console will automatically be populated with the necessary information, such as transaction details, regulatory requirements, and investigation deadlines.

Alternatively, you can now also dispute card transactions directly from Posted Transactions (detail view) in the Synctera Console rather than creating a new Case from scratch, allowing your customer-facing teams to more easily submit and track disputes, providing better customer outcomes. 

Webhook events are available for all dispute lifecycle updates and postings so you can monitor each step of the dispute process, highlight the status of a dispute, and send customer notifications.

You can read more about the new dispute process here. 

‍

ACH improvements to further support Earned Wage Access and payroll

Standard Entry Class (SEC) codes are used in ACH transactions and maintained by the ACH network’s governing body, Nacha, to identify transaction types, determine authorization requirements, and facilitate the proper handling of transactions.

Outgoing ACH transactions can now be sent with the Prearranged Payment and Deposit (PPD) SEC code. This SEC code allows customers to credit external consumer accounts with earned wages regularly using the appropriate ACH classification, aiding in specific Earned Wage Access (EWA) solutions.

The choice of SEC code used in a transaction can significantly impact the end-user experience, depending on the external bank. Some banks process deposits more quickly when they are classified using the PPD code. Additionally, some external banks charge maintenance fees without a direct deposit set up. Using the PPD code can now help avoid these end-user fees by treating these ACH transactions as payroll deposits. 

Please note that customer disclosures and bank approval are required to use the PPD code.

‍

Track subscribed webhooks in the Console 

Using the Synctera Console, developers and technical teams can now monitor and resend webhooks they’re enrolled in. Importantly, they can view webhook status, review the event, and even resend the webhook, bypassing any manual intervention normally required.

If you have any questions or would like to discuss these updates, please reach out to your customer success representative or contact our team here.