Changelog: 2019-Aug-02

Pushed to production :white_check_mark:, Pushed to Sandbox :beach_umbrella:.

Critical Updates

  • :white_check_mark: Accounts: Added lock_overdrawn_users routine to lock any user accounts that are overdrawn by -$300 or more.

  • :white_check_mark: Account Aggregation (Bank Logins): We now support the ability to link to and extract data from over 2500 banks.

  • :white_check_mark: Operations: Our Customer Success and Integration Engineer teams will no longer complete ANY API actions on behalf of platforms. This decision was made to further improve information security standards, both internally and for our platforms. [Note: Added 2019-Aug-08]

  • :white_check_mark: Card Issuance: Cards subnets (and legacy CARD-US nodes) can now only be set to ACTIVE status a maximum of 10 times per week. This change should prevent unintended or non-standard use of our Update Card Status API call. [Note: Added 2019-Aug-12]

New Features

  • :white_check_mark: Client Dashboard (Transaction Creation): Create Transaction form now provides the ability to query nodes by nickname or by ID.


  • :white_check_mark: ACH (Linking ACH Accounts): Added info.bank_code, info.bank_hlogo and info.bank_url to the ACH-US response for both Bank Logins and AC/RT Number linked external accounts.

  • :white_check_mark: Accounts (Duplicate Accounts): Improvements to duplicate user account detection (duplicate_user_check) logic to reduce incidence of false positives.

  • :white_check_mark: Fraud Monitoring: Refinements to fraud monitoring for issuance processing transactions, specifically for business BIN logic.

  • :white_check_mark: Client Dashboard (User Detail): Updated description text for the “make searchable” checkbox (on a user’s basic information tab) to better indicate that the checkbox toggles the is_hidden property.

  • :white_check_mark: Client Dashboard: Updates to sign-in flow.

  • :white_check_mark: System (Reliability): Reliability improvements to database transactions to reduce (ideally eliminate) any temp balance discrepancies

  • :white_check_mark: Webhooks (Reliability): Webhook delivery reliability improvements.

  • :white_check_mark: RDC (Fraud Monitoring): Improvements to RDC velocity checks for improved fraud detection (e.g. with repeat check submissions).

  • :white_check_mark: Accounts (Subnets): Subnets now require a document_id associated with the underlying node upon creation to prevent them from getting stuck in pending status. Refer to Create Node API call for more details.


  • :white_check_mark: Client Dashboard (External Accounts): Fixed display issues with meta information tied to certain External-US nodes.

  • :white_check_mark: Client Dashboard (Card Issuance): Fixed an issue with Ship Card form where the expedite value wasn’t toggling properly.

  • :beach_umbrella: Client Dashboard (Card Issuance): Fixed reset card patch call on sandbox.

  • :white_check_mark: Client Dashboard (User Detail): Fixed an issue with display of “Change Permission” button.

  • :white_check_mark: Client Dashboard (Documents): Fixed a Dashboard UI issue with properly displaying documents as invalid or missing.

  • :white_check_mark: Client Dashboard (Statements): Fixed issue with monthly statements opening broken links.

  • :white_check_mark: Loans (Subnets): Fixes to transaction limits for LOAN-US card subnets.

Can I assume that if the change is pushed to production, it is also pushed to the sandbox?
Thank you

Hi @dustin yes that is true.