Changelog: 2020-Mar-16

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

  • Users (Enhanced Due Diligence): Synapse is in the process of updating our enhanced due diligence (EDD) process for flagging high-risk users.
    • This process is still undergoing some refinement internally, and has yet to be pushed to either Sandbox or Production.
      • This change will not be pushed to production until first announced to Platforms (e.g. via a future Changelog or vis email), but Platforms should prepare for when this push is eventually live.
    • However, once this change is live Platforms will no longer be able to directly lock users and will only be only be able to directly close users based on user requests (i.e. permission_code: USER_REQUEST).
      • The Swap Duplicate Users API call can also be used to indirectly close duplicate users (subject to the requirements of that call).
      • Otherwise, Platforms will need to flag users for potential closure with this new EDD process. Our Compliance team will review flagged users and make the final decision to either close or reinstate each user on a case-by-case basis.
    • For details about how the process will work, please refer to Enhanced Due Diligence.
      • Additionally, refer to this resource for a basic breakdown of the EDD user flag codes used in this process.

New Features

  • :white_check_mark: Native Card Transactions (POS Transactions): Updates have been made for Native Card Transactions to reflect point-of-sale information including:
    • Terminal Info (terminal_info) includes captured card data at the terminal where the POS was made.
      • Information includes if the transaction was conducted by a third party (terminal_info.attenance, terminal_info.location, terminal_info.operator), and card capabilities (card_input_capability, card_retention_capability, type)
    • Presentment Info (presentment_info) includes how the card was presented at the POS (presentment_info.card_presence, presentment_info.cardholder_presence, presentment_info.security_concern) and the stage of verification of the transaction (presentment_info.type)
    • Condition Code (condition_code) includes the condition under which the transaction takes place at the point-of-sale (e.g. normal presentment, customer not present, mail or telephone order)
      • Please note that this will often be null and similar values are represented in presentment_info
    • Additional information includes how the card pin was entered at the terminal (pin_entry_mode), and how the PAN was collected (pan_entry_mode)

Improvements

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

    • PDF statements have added a locations column for all node types (e.g. previously CARD-US was a supported node type).
    • Updates will be made in the future to improve statement PDF formatting (e.g. improvements for better readability, font sizing, and other layout improvements).
  • :beach_umbrella: Accounts (Duplicate Users): Open users will now have the CLOSED error messages on extra.note (e.g. duplicate_name_and_address --- CLOSED due to duplicate Name and Address. userIDs open: [user_id]. userIDs closed: [user_id]).

    • A closure message was previously only included for a user closed by our duplicate user detection logic, but will now be provided with the user left open as well to help provide context (e.g. when a Platform may wish to use the Swap Users API call to switch a currently open user it with one of its closed duplicates).
    • Refer to View User w/ Full Dehydrate for more details.

Fixes

  • :white_check_mark: Accounts (Duplicate Users): Duplicate user logic with respect to SSNs / TINs has been updated to prioritize the user with most recent activity as expected. Previously all accounts with duplicate SSNs / TINs were being closed by default.