Changelog: 2020-Mar-30

Please Note: Additional items may be appended to this Changelog in the near future once finalized.


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

Critical Updates

  • :white_check_mark: Statements (Statements Generation): Further updates have been made to statements to include the following:

    • Statement files in JSON & CSV formats that are larger than a selected threshold will be separated into multiple smaller files and returned as an array. (e.g. csv: [csv_url1.csv, csv_url2.csv, csv_url3.csv] or json: [json_url1.csv, json_url2.csv, json_url3.csv]).
    • Improved CSV format to better display fees
      • Please note that applicable fees that do not impact the net amount of a transaction (e.g. fixed_rate, variable_rate) will remain listed on the CSV and show an amount of (0) zero to reflect their net impact.
    • Improved JSON format to include more details in the summary and transactions sections (e.g. withdrawals, ending balance, etc.) including the total number of the following:
      • CREDITS (e.g. CREDITS: 77)
      • DEBITS (e.g. DEBITS: 60)
      • REVERSALS/RETURNS (e.g. RETURNS: 3)
    • Refer to View Node Statements for more details
  • :white_check_mark: Nodes and Subnets (Status Codes): Status codes have been added to automate both the reopening of nodes and subnets (as applicable) when a user is reopened or unlocked (e.g. after being previously CLOSED or LOCKED).

    • When updating a node’s allowed value (e.g. via the Update Node API call), a relevant allowed_status_code will be required.

      • Many of these will be applied by Synapse behind the scenes (e.g. “ISSUER_DIRECTED”,“ACCOUNT_CLOSED”, or “ACCOUNT_LOCKED”), but Platforms can supply “USER_REQUESTED” node status code.
    • When updating a subnet’s status value (e.g. via the Update Native Card Status API call), a relevant status_code will be required.

      • Many of these will be applied by Synapse behind the scenes (e.g. “ACCOUNT_CLOSED”,“ACCOUNT_LOCKED”,“FRAUD_ALERT”), but Platforms can supply “USER_REQUESTED” subnet status code.
  • :white_check_mark: Transaction Return Fees (Return Fee Nodes): Platforms can now specify a Return Fee Node (preferences.return_fee_node_id) from which to debit return fees.

    • This node can currently be set in your Platform controls by Synapse, but an upcoming change should allow this node to be specified from the Client Dashboard in the near future.

New Features

  • :beach_with_umbrella: Crypto Wallets (DAI): Support for the Dai (extra.asset: DAI) stablecoin cryptocurrency has been added for Crypto Wallets (CRYPTO-US) in Sandbox.

Improvements

  • :white_check_mark: Client Dashboard (Bank Transactions): The Bank Transactions tab has been updated to include the following:

    • For nodes that have a transactions list, a bank transactions table has been added that includes all transactions for the node (e.g. for ACH-US, WIRE-US, etc.)
    • A status column has been added to show if the transaction is in a pending or settled state.
  • :white_check_mark: Client Dashboard (Incoming External Wires): Client Dashboard now displays origination_country for domestic wire transfers initiated by external parties (i.e. not by Synapse).

    • Incoming external domestic wires will have “US” set for their origination country.
    • Incoming external international wires will have the appropriate foreign country code (e.g. “UK”, “CA”, etc.) set for their origination country.
    • Country codes will follow ISO 316601 Alpha-2 Country Code standard.

Fixes

  • :white_check_mark: Client Dashboard (Users): A minor fix has been made to the date formatting on the User detail page.