Webhook Update: Retries

Aeropay has added retry functionality to our webhook events. These details can be found here: https://dev.aero.inc/docs/webhooks-1#webhook-retries

If your webhook endpoint temporarily can’t process events, Aeropay will automatically resends the undelivered events to your endpoint, increasing the time for your webhook endpoint, with exponential backoff and jitter, to eventually receive and process all events.

Aeropay will retry webhooks if:

• Callback URL fails to respond within 3000ms
• Callback URL fails to respond with 200 status code

Aeropay will attempt up to 5 total retries.

SFTP Report Update

As part of recent reporting enhancements, Aeropay has added an explicit RTP identifier. As of October 1st 2025, a new column will be added to the daily SFTP reports called ACH/RTP Identifier. Accepted values in this column are either RTP or ACH depending on which rails the payment was processed through.

Ensure your reporting systems are setup to properly handle this change and accept this new column.

Sample Updated Report (.csv)

transactionid,Batch Date,Batch ID,status,User ID,First Name,Last Name,Email,merchantid,merchantlocationid,title,amount ($),apfee ($),Created Date,Modified Date,externaltransactionid,handshaketype,deviceid,paymenttype,attributes,useraccountid,merchantaccountid,internalamount,uuid,Merchant Reputation Status,ACH/RTP Identifier
"1,759,497",2025-09-05 17:01:00,182747,processed,"1,103,173",Pat,Jones,[email protected],930,900,Online Transaction,250,1,"September 4, 2025, 7:28 PM","September 4, 2025, 7:28 PM",fiservpx:634296,po,,payout,,"750,183",651,1,4281f386-d487-4115-8d32-9c94da9c7161,Standard,RTP
"1,759,121",2025-09-05 17:01:00,183691,processed,"1,803",George,Clooney,[email protected],930,900,Online Transaction,20,1,"September 4, 2025, 7:28 PM","September 4, 2025, 7:28 PM",,po,,payout,,"2,452",651,1,2ab9dcec-d3de-4a3b-8114-dbdb2bd28aa4,Standard,ACH

New Merchant Portal URL

As part of recent architecture updates, Aeropay released a new URL for the Aeropay Merchant Portal in both sandbox and production. Beginning Monday, July 14th 2025, Aeropay will begin forwarding all old portal URLs to the new URL format.

While the old URL format will continue to be active as it forwards to the new site, we recommend updating any bookmarks or saved links to our new portal URL. Please see the URL changes below:

Enhancements

Updated documentation to more accurately portray response values

New Sandbox Environment

Aeropay released a new sandbox environment for testing purposes which will replace Aeropay's existing staging environment. This new environment is more stable and efficient, providing more reliable testing and faster integrations.

What will happen to my test data in staging?

During this transition period, Aeropay will share data between the sandbox environment and staging environment to ensure a smooth transition between environments if this change is occurring during your integration.

When will staging be deprecated?

The staging environment will be available until May 22nd, 2025, at which point all Aeropay testing must use the sandbox environment. This means updating any testing API URLs to sandbox and using the new sandbox merchant portal.

🚀 Aerosync Web SDK v1.1.1 - Release Date: 4/22/2025

✨ New Feature

Embedded Bank View (Optional)
You can now embed a list of Aerosync-supported banks directly into your webpage using the new embedded view feature. This offers a smoother and more integrated user experience.
Learn more here: https://dev.aero.inc/docs/embedded-view

🐛 Bug Fixes

Fixed flashing issue when launching the widget in dark mode.
Resolved unintended onClose event trigger during successful bank linking.
General code cleanup and several minor bug fixes for better performance and stability.

⚠️ Breaking Changes (for v1.1.0 and earlier)

If you're upgrading from v1.1.0 or below, take note of the following breaking changes:

openWidget() ➡️ renamed to initAeroSyncWidget()
– Use the new function name to initiate the widget.
Widget Config: id ➡️ renamed to elementId
– Update your HTML reference in the widget configuration.
Event Handling Change:
– Now, only onSuccess() is triggered after a successful bank link and widget close.
– Previously, both onSuccess and onClose were fired together.
– Make sure to listen to onSuccess() to handle success actions like updating your UI or navigating to the next step.

ℹ️ Note for v2.x.x Users
If you're already using v2.x.x, no changes are needed.
This update is specifically targeted at 1.x.x clients who haven’t migrated yet.

Enhancements

Aeropay SDK

• Updated end user experience across all Aeropay SDK integrations and payment links. These changes include a new landing page UI with more scalable customization capabilities.

Bugs Fixed

Merchant Portal

• Fixed bugs affecting search for preauthorized transactions by user name or transaction id

Enhancements

Aeropay

• New aeropassUUID parameter added to response to POST /user and GET /user. AeropassUUIDs are unique identifiers for users across Aeropay's suite of products.

Features

Merchant Portal

• Updates to merchant portal user experience and layout

Bugs Fixed

Merchant Portal

• Fixed bug blocking merchant users from searching preauth transactions by uuid

Enhancements

Aerosync

• Bolstered user security and blocks against bots

New Feature

Aeropay User Reputation APIs gives merchants the ability to update user statuses on their platforms, allowing their users to be promoted to trusted status, or demoted to blocked. These updates can be made both via our APIs, or in the Aeropay merchant portal.

This release includes 2 new APIs and a new webhook topic:

• POST /merchantReputation
• GET /merchantReputation
• merchant_reputation_updated webhook topic