[georgeweiler]

Explanation

The app needs to know when a virtual bank account transaction is new or has changed status, without storing amounts or bank details and without reporting the same change twice.

RampsController persists autorampTransactionRecords: for each autoramp, the epoch ms of the first successful fetch and the last seen status string per transaction id. diffAutorampTransactions is pure. The first successful fetch (including an empty one) seeds the record and calls nothing. Later fetches report a new id or a different status string, including a status that moved backwards or skipped intermediate values. A transaction missing from the page stays in the record.

refreshAutorampTransactions loads the newest page (sort_order=desc, page_size 50, no pagination), writes the next record, then calls the optional trackAutorampTransactionStatusChanged constructor callback once per change. previousStatus is omitted for a new id. A failed fetch writes nothing. Concurrent calls for the same autoramp share one request. Removing an autoramp, replacing the autoramp cursor, or discarding a foreign VBA session clears the matching records. A fetch still in flight when that autoramp leaves the cursor does not write the record or call the callback.

This is an analytics signal, so it is a callback rather than a RampsController messenger event. orderStatusChanged and autorampStatusChanged stay messenger events because the client uses them for more than tracking.

NeoBankService.listAutorampTransactions accepts an optional pageSize. Omitting it keeps the previous query.

References

• Mobile adoption: feat(ramp): track Money VBA Transaction Updated metamask-mobile#38078

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

BREAKING: RAMPS_CONTROLLER_REQUIRED_SERVICE_ACTIONS now includes NeoBankService:listAutorampTransactions. Hosts that spread that list pick it up on the package bump. Hosts that copy the action list by hand must delegate it.

---

Note

Medium Risk
Introduces a breaking messenger delegation requirement and new persisted VBA transaction state with analytics callbacks; behavior is guarded but hosts must wire the NeoBank action and handle migration of persisted state.

Overview
Adds persisted autoramp transaction status tracking so hosts can learn when a VBA deposit transaction is new or its MoonPay status string changed, without storing amounts or firing duplicate analytics.

RampsController gains persisted autorampTransactionRecords (per autoramp: syncedAt plus last-seen status per transaction id), the pure helper diffAutorampTransactions, and refreshAutorampTransactions, which loads the newest transaction page (page_size 50), updates the record, then invokes optional constructor callback trackAutorampTransactionStatusChanged once per new id or status change (previousStatus omitted for new ids). The first successful fetch only seeds the record; failed fetches leave it unchanged; concurrent refreshes per autoramp dedupe to one request; records are cleared when an autoramp is removed, the cursor is replaced, or a foreign VBA session is discarded, with in-flight fetches not re-writing removed autoramps.

NeoBankService.listAutorampTransactions accepts optional pageSize (page_size query). Breaking: RAMPS_CONTROLLER_REQUIRED_SERVICE_ACTIONS now requires NeoBankService:listAutorampTransactions delegation. New messenger action RampsController:refreshAutorampTransactions and related types are exported from the package.

^{Reviewed by Cursor Bugbot for commit 86c201b. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 68becb2. Configure here.}

[matteyusys]

Proxy has /autoramp-transactions/ids for targeted refresh. Do we have any plan to use it (e.g. after push) vs forever listing?