Changelog: 2020-Jul-20

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

  • Client Dashboard (Versioning): Though Client Dashboard Version 2 is currently live, scheduled sunsetting of Client Dashboard Version 1 has been postponed from July 27th to August 10.

  • UIaaS (Version 1): The scheduled date for UI as a Service (UIaaS) Version 1 deprecation and end of support (in favor of Chatbot services) has been postponed from July 27th to August 28th.

  • Client Controls (Versioning): Client Controls Version 1 and Version 2 are still scheduled to be sunset on July 27th.

  • Data Enrichment (Version 1.0): Data Enrichment 1.0 is still scheduled for deprecation on 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 and that Platforms will instead need to collect merchant information provided from Data Enrichment 2.0 (i.e. 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 on July 27th August 10th and Platforms will be expected to follow the new Enhanced Due Diligence flow. [Note: Edited 2020-July-27]

  • API Calls (Version 3.0): Version 3.0 APIs are still scheduled to be sunset on July 27th.

  • Transactions (Merchant Disputes): The former dispute APIs will are still scheduled to be sunset on July 27th.

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

  • :white_check_mark: Notifications (New Notifications): Added notifications for user permission changes, including when user permissions change to LOCKED (message_type: locked_positive_balance, message_type: locked_zero_balance, and message_type: locked_negative_balance) and when permissions change from PENDING_REVIEW to the SEND-AND-RECEIVE (message_type: send_receive).

Features

Improvements

  • :white_check_mark: RPPS (View Billers): Added default values for pagenation (?page=1) and result limits (?limit=20) for View Billers RPPS call.
  • Chatbot: New errors for unauthorized payloads (e.g. agent_not_authorized and user_not_authorized to go along with existing client_not_authorized error).
  • :white_check_mark: Users (Name Validation): Enhances name validation to catch common titular names (e.g. Baron, Princess, etc.)
  • :white_check_mark: Native Card Issuance (Transaction Decisioning & Instant Auth): Improved internal logging of Platform responses to Transaction Decisioning & Instant Auth webhooks.
  • :white_check_mark: Notifications (Email Notifications): Now notifications will be addressed from Platform email rather than Synapse email.
  • :white_check_mark: Nodes (Negative Balance Reconciliation): Accounted for additinoal negative balance reconciliation cases to avoid unwanted cancellations (e.g. for self-funding attempts from another node owned by the same user to restore a the negative balance to a positive balance).
  • :white_check_mark: Client Dashboard (Dates): Human-readable dates now provided when downloading User, Node, and Transaction tables from the Client Dashboard.
  • :white_check_mark:

Fixes

  • :beach_umbrella: Chatbot (Postmortem Attachments): Fix for postmortem.attachments when postmortem unavailable.
  • :white_check_mark: RDC (RDC Transaction Results): Fixed typos in field names of results for Create RDC Transaction call.
    • orignal_check_back is now original_check_back
    • orignal_check_front is now original_check_front