Changelog: 2020-Apr-27

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: Client Dashboard (Versioning): Client Dashboard Version 2 is now live. Version 1 is scheduled to be sunset in the next 90 days (scheduled date is currently July 27th). Please note that once V1 is sunset, the URL will redirect to the latest version of the Client Dashboard.

  • Client Controls (Versioning): Client Controls Version 1 and Version 2 will be sunset in the next 90 days (scheduled date is currently July 27th).

  • Data Enrichment (Version 1.0): Data Enrichment 1.0 will be deprecated in the next 90 days (scheduled date is currently July 27th).

    • This means that Data Enrichment 1.0 fields (e.g. to.meta.merchant_category, to.meta.merchant_logo, to.meta.merchant_name, to.meta.merchant_official_page, etc.) will no longer be provided with transaction objects.
    • You will instead need to collect merchant information provided from Data Enrichment 2.0 (in the to.meta.enriched_info object). Refer to Enrichment for more details on Enrichment 2.0.
  • Users (Enhanced Due Diligence): The former process of locking and closing user accounts will be retired from the API in the next 90 days (scheduled date is currently July 27th). Platforms will need to follow the new Enhanced Due Diligence flow.

  • API Calls (Version 3.0): Version 3.0 APIs will be sunset in the next 90 days.

  • Users (File Transmission): The URL will be sunset in the next 15 days (scheduled date is currently May 11th) and replaced with for transmitting URLs.

    • Please note that the provided URLs will only be valid for 24 hours before expiring.
    • Please also note that this file transmission URL should be readily applicable to all files on the user object, and should be updated in the future to include other common files (e.g. statements).
  • Database (Migration): Please note that we will be performing a database migration on production, Sunday, May 3rd. Platforms should not expect any downtime, and will be able to see updates on the statuspage.

  • :white_check_mark: Legacy Card Issuance (Negative Balance Reconciliation): Negative balances for Legacy Cards (CARD-US nodes) will now immediately be reconciled and set the user account as LOCKED.

  • Transactions (Merchant Disputes): The former dispute APIs will sunset in the next 90 days (scheduled date is currently July 27th).

  • Native Card Issuance (Daily Cash Limit): The allow_cash_transactions boolean in native card preferences is expected to be deprecated in the next 90 days (scheduled date is currently July 27th) in favor of a new daily_cash_limit that can be set to a custom amount.

  • :white_check_mark: KYC (Proof of Address): A new Proof of Address (PROOF_OF_ADDRESS) physical document verification model is expected to be pushed on April 30th.

    • You can find information and file format requirements (e.g. submitted document must be a supported bank statement or utility bill, preferably as a PDF, in portrait orientation, with matching name and address from base doc, etc.) here.
  • UIaaS (Version 1): UI as a Service (UIaaS) Version 1 will be deprecated with support ending in the next 90 days (scheduled date is currently July 27th) in favor of Chatbot services.

  • Bank Logins (Chatbot Bank Logins): The deadline to transition from API Bank Logins to Chatbot Bank Logins (mentioned in March 2nd Changelog) has been extended from April 30th to May 29th.

  • :white_check_mark: Client Dashboard (On-Boarding): The On-boarding site is now live in the production version of the dashboard. New fields have been added to the on-boarding form submission process including steps to guide you through the process of setting up a billing account, reserve account, uploading necessary documents, setting up information about the company, and providing beneficial owner information. New fields have been added including updates reflected in the following:

    • Beneficial Owner (UBO) form
      • Ownership Percentage (ownership_percentage) (e.g. between 0% and 100%)
      • Title (title) (e.g. “Chief Executive Officer”)
      • Entity Relationship (entity_relationship) (e.g. either beneficial owner or controlling person)
    • Financial Information form (under Company Information)
      • Company Activity (company_activity) (e.g. MSB, crypto, lending, etc.)

New Features

  • :white_check_mark: Client Dashboard (Zendesk Tickets): The Zendesk ticket integration with client dashboard is now live.

    • Please note that platforms need to set a zendesk_code value within their client preferences to have access to the “Tickets” tab, where they can view tickets with Synapse, create new tickets, and reply to previous tickets.
  • :white_check_mark: Client Dashboard (Enhanced Due Diligence): Added the ability to flag an end-user and to submit their required EDD documents.

  • :white_check_mark: Client Dashboard (User Interface): We will begin the process of converting the current UI to a newer version, beginning with select forms (e.g. create user, node, and transactions). Please note that further updates will be pushed that improve the client dashboard user interface in the coming weeks.


  • :white_check_mark: Accounts (Agreements): Mastercard Cardholder agreements and Custody agreements have been updated when generating PDF agreements at node creation to maintain compliance standards.
    • Please note that Crypto agreements will be updated as well in the near future.