Changelog: 2019-Sep-27

Please Note: Additional items have been appended to this Changelog post-publication.

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

Critical Updates

  • :white_check_mark: Client Reports (UARs): For platforms who are required to file Suspicious Activity Reports (SARs) with FinCEN, the Client Report generated via the POST /v3/user/client/reports API call can now provide an Unusual Activity Report (UAR) as a supplemental aid.

    • The uar_report[ ] array will supply the transaction_id and status_code (e.g. “PER CUSTOMER REQUEST”, or “R08”, or “Q10-H [WIRE ARRIVED]”, etc.) for each transaction listed in the report.
    • The UAR provides Platforms a listing of potentially unusual activities as flagged under Synapse’s automated controls. Platforms should not rely solely on this report to comply with obligations related to supervising Suspicious Activities. Platforms should further investigate any activities flagged by Synapse as unusual to verify if they are indeed suspicious activities that warrant filing SARs. Synapse is not liable for any failure to communicate an SAR or for any improperly submitted reports.
  • :white_check_mark: Statements (Statement Generation): Unless specified differently in your platform contract, monthly statement generation currently adheres to the following default timing:

    • Revolving LOAN-US nodes will provide prior-month statements by the 7th of the month. This timing ensures that interest accrual grace period allotted to users (set by regulatory requirements) is honored within the statement delivery month.
    • For other account types prior-month statements are, by default, made available by the 15th of the month.
    • These clarifications are now reflected on both the Statements page and the Loan Interest page in our API Docs. For a short time these pages listed contradicting dates but have been fixed.
  • :white_check_mark: Accounts (Agreements): The type for has been changed from LOAN_AGREEMENT to NODE_AGREEMENT.

New Features

  • :white_check_mark: Loans (Revolving Loans): New methodology for calculating and tracking accrued interest for revolving loans. [Note: Added 2019-Oct-01]

    • Please note that you can view accrued interest periodically by viewing the statement for the LOAN-US node generated on a monthly basis or within the info.interest.accrued field in the response to the View Loan Details API call.
    • Click here for more details about revolving loan interest accrual.
  • :white_check_mark: Card Issuance (Dispute Transaction): Added ability to include additional attachments in new dispute_attachments array with the dispute form when disputing a card transaction (either with legacy card issuance or with native card issuance).

    • Please note that attachments included in the dispute request must be passed as Base64-encoded strings.


  • :white_check_mark: Card Issuance (Dispute Transactiojn): Disputes can now only be filed for transactions with SETTLED status. [Note: Added 2019-Oct-01]

  • :white_check_mark: Card Issuance (Dispute Transaction): When a user files a transaction dispute, provisional credit will by default now be provided within 5 business days for existing users. Provisional credit was previously provided immediately by default for existing users. [Note: Added 2019-Oct-01]

    • Please note that provisional credit will be issued to new users within 20 business days by default.
  • :white_check_mark: Accounts (Agreements): CARD-US, DEPOSIT-US, IB-DEPOSIT-US, and IC-DEPOSIT-US nodes now generate PDF agreements at node creation.

  • :white_check_mark: Transaction (Transaction Status): When applicable transactions are updated with transaction status of queued (QUEUED-BY-SYNAPSE), canceled (CANCELED), or returned (RETURNED) , the respective transaction queue code (e.g. Q02 ), transaction cancellation code (e.g. C08 ), or transaction return code (e.g. R01 , CR01 , IR01 , CHR01 , or WR01 ) will now be provided in the new recent_status.code field. The code and a brief description will continue to be provided in the recent_status.note field. Refer to the View Transaction API call for more details. [Note: Added 2019-Oct-02]


  • :white_check_mark: Fixed issue where force_refresh query parameter for the View ACH Account API call would activate previously inactive ACH nodes.
    • Now passing force_refresh with the call will update balances and get other ACH node information, but will not change the node status.