Changelog: 2019-Dec-09

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: Accounts (Duplicate Users): We have refactored our duplicate user (get_duplicates) detection logic to better determine the appropriate user to mark as a duplicate and close, as well as our internal process for switching a given active user account with one of its previously closed duplicates.

    • Implications
      • The changes below will be pushed to production (internally) in the near future. This means platforms should be aware that duplicate account closures may occur.
      • Platforms will be expected to perform basic investigations about any closures (e.g. view the closed users with full dehydrate as outlined below to determine closure reason, identify possible user accounts to swap, etc.), and will need to reach out to Synapse if they require assistance with affected user accounts based on their investigations.
      • Once the public versions of these APIs are live, API reference links will be added to the Changelog.
    • Duplicate User Detection Logic
      • This new logic will prioritize the account with the most recent account activity within an internal timeframe set by Synapse.
      • Most recent activity is determined (in order of priority) by the most recently created transaction (recent_status.date), or by the most recently created node (created_on).
        • If neither are available then most recent activity is determined by the date the user was last updated (extra.last_updated.$date).
      • Additional checks will be performed to determine duplicate accounts within the same CIP tag based on name, email, address, date of birth (DOB), driver’s license, and SSN, and for LOCKED user accounts across all CIP tags.
    • Swap Users
      • “Swapping” user accounts may be appropriate in certain cases when re-opening a previously closed user account is preferred over retaining a newer duplicate user account. The active user account will be CLOSED while the inactive user account (i.e. the account being “swapped in”) will be re-opened with UNVERIFIED permissions (i.e. KYC verification will need to be re-run for the user).
      • Please note below the conditions under which a user swap will not be performed:
        • If either user account has LOCKED or MAKE-IT-GO-AWAY permissions (invalid_permission).
        • If both user accounts are UNVERIFIED.
        • If both user accounts are active (i.e. both have SEND-AND-RECEIVE permissions), as the user accounts are duplicates and one should be closed.
        • If the user accounts fall under different CIP tags (invalid_tags).
        • If the user accounts are for different user types (e.g. business and personal accounts) (invalid_swap).
    • Note on Viewing Closed Users
      • You can perform a full dehydrate on a closed user and check the extra.note field to view the closure reason.
      • Notes will contain closure reasons listed above (e.g. "CLOSED due to duplicate Name and Email” or “CLOSED due to duplicate SSN”). This will also include the ID of the user.
  • :white_check_mark: Cards (Public Keys): New Public Encryption Keys have been released for linking external cards (transaction node with "type": "INTERCHANGE-US"), and for Legacy Card Issuance (subnet with "account_class": "DEBIT_CARD") to maintain PCI Compliance standards related to rotating encryption keys for security purposes.

New Features

  • :white_check_mark: Client Dashboard (Subnets Table): The Subnets Table for account and routing numbers (Checking/Savings), in addition to displaying subnet status, will now also allow you to edit subnet status.
    • If you hover over a row containing an account and routing number subnet, you should be able to see the option to “Change Status” for the subnet.
    • Please note that your platform can toggle ACTIVE / INACTIVE status for a subnet, but that changing a subnet’s status to TERMINATED will be irreversible.

Improvements

  • :white_check_mark: KYC (Duplicate Users): Updates have been made to improve our internal duplicate user detection based on facial vectors. This process is separated from duplicate user checks mentioned above.

  • :white_check_mark: KYC (Naming Convention): We will be changing our references to blacklisted items (e.g. from blacklisted users to blocked users) in an effort to align with more accurate and modern classification.