Changelog: 2020-Jan-06

Please Note: Additional items have been appended to this Changelog post-publication.


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

Critical Updates

  • :white_check_mark: Transactions (International Wires): Outgoing International Wire transfers (WIRE-INT) now require a minimum transfer amount of $1,000 to be processed. Outgoing International Wires under the minimum amount (i.e. for any amount less than $1,000) will not be sent, and will be cancelled (with recent_status.note “[Returned on Credit] UTA UNDER DAILY MINIMUM LIMIT OF $1,000.00 USD”). Please note that this requirement only applies for outgoing International Wires and not for incoming International Wires.

    • Refer to Wires for further reference.
  • :white_check_mark: KYC (ID Verification Reason Codes): Further updates have been made to improve the machine learning model for ID Verification (IDV). More descriptive reason codes will now be provided with rejected documents based on the quality of the submission.

    • Criteria that will cause an ID to be rejected with SUBMITTED|INVALID status include:
      • Submitted image does not meet file submission expectations:
        • File format is not jpg/jpeg or png as expected (wrong_file_extension)
        • Image quality (poor_image_quality)
        • Image missing or empty (image_not_found)
        • Image lacks color (black_and_white_image) or RGB channels (palettised_image)
      • ID does not meet essential information qualifications:
        • Name from ID does not match base document name (name_mismatch)
        • DOB from ID does not match base document DOB (dob_mismatch)
        • Face on ID is not detected (face_undetected), which can occur if eyes are obscured in submitted image (e.g. due to glasses or camera flash)
    • Criteria that will cause an ID status to remain in SUBMITTED|REVIEWING status (i.e. flagged for manual review by Synapse’s Compliance team) include:
      • IDs submitted with a corner missing/obstructed (e.g. by a user’s thumb), an unexpected ID layout, or are flagged as a potential fake will be flagged with reason code flagged_for_failing_security_feature.
      • IDs with extracted text similar to a user in a blocked database (flagged_for_potential_fraud) will also be flagged for manual review.
      • Items flagged for manual review will generally be reviewed within 2 business days.
    • Please note that these improved security features should better discern between poor quality and good quality ID submissions. Additionally poor quality submissions should be designated SUBMITTED|INVALID faster, there should be a lower incidence of false positive SUBMITTED|VALID IDs, and the number of SUBMITTED|REVIEWING IDs should be greatly reduced.
    • Please also note that the runtime for processing IDs may increase from 15 seconds to 20 seconds due to the extra processing required, though decisioning should take less than 1 minute. Future refinements should reduce this runtime in future updates.
    • Refer to Sub-Document Statuses for more details.
  • :white_check_mark: KYC (EIN Document Verification Reason Codes): Similar to the IDV Reason Code changes above, the machine learning model for EIN Verification will also return descriptive reason codes with rejected EIN documents based on the quality of the submission.

    • Criteria that will cause an EIN Document to be rejected with SUBMITTED|INVALID status include:
      • Submitted image does not meet file submission expectations:
        • File format is not pdf, jpg/jpeg, or png as expected (wrong_file_extension)
          • Please note that original pdf format is highly recommended (e.g. not a secondary scan of the document).
        • Image missing or empty (image_not_found)
        • Image lacks RGB channels (palettised_image)
      • EIN document does not meet essential information qualifications:
        • Company name on document does not match company name on base document (company_name_mismatch)
        • Tax ID Number (TIN) on document does not match base document TIN (tax_id_mismatch)
          • EIN document should not be altered in any way (e.g. TIN number crossed off and updated to a new number) and will cause the document submission to fail.
        • IRS logo on document not detected (irs_logo_undetected)
    • Please note that EIN Document verification does not currently have criteria that will cause the document to be submitted for manual review.
  • :white_check_mark: Subnets (Transactions): Subnet credits for external (EXTERNAL-US) ACH and Wire transactions are now monitored to compare the meta_name to the base document for the user as an added measure to ensure users are not receiving funds that do not belong to them (e.g. credits intended for a business to an individual account).

    • When the meta_name does not match the end user’s name on file, the transaction will now queue for review. The transaction will either be settled or returned as a result of our review.
      • Additional details, including the ratio match between the provided name and the base document name will be provided in queue_message.
    • If after manual review the transaction is ultimately returned, it will have one of the following return codes:
      • [Returned on Debit] R03 – No Account/Unable to Locate Account
        • [Previously posted as different code. Amended on 2020-Jan-08]
    • Please note that when setting up a payment, users should be sure to include accurate information (e.g. recipient’s info) to avoid unexpected returns based on this new logic. The meta_name should be the name of the intended recipient which will be compared to the recipient’s base document.

New Features

  • :beach_umbrella: The Update Preferences API call for native card transactions now allows platforms to set both a card’s daily maximum transaction limit (preferences.daily_transaction_limit) and whether to allow the card to perform cash transactions (preferences.allow_cash_transactions).
    • If preferences.allow_cash_transactions is set to false, cash transactions (e.g. CASH, CASH_WITH_DISBURSEMENT, and QUASI_CASH) will be blocked.
      • If a cash transaction is attempted when preferences.allow_cash_transactions is set to false, new error message cannot_enable_atm – card not allowed to enable ATM activity since its restricted at the platform level.
        [Previously posted as in Production. Amended on 2020-Jan-07]

Improvements

  • :white_check_mark: KYC (ID Verification): Additional improvements to the ID Verification including:

    • Updated document and sub-document models with increased detection accuracy for document type and subfields within an ID (name, DOB, issue date, etc.).
    • Improved text accuracy for matching user name and DOB, as well as extraction of other information (e.g. DLN, issue date, expiration date).
  • :white_check_mark: Chatbot (Bank Logins): Platforms participating in the Chatbot for Bank Logins (Account Aggregation) closed beta can now configure the chatbot to provide a message when the user exits the chatbot flow (i.e. closes the chatbot).

    • To provide a custom message, simply provide the message parameter to the optional onExit function. Please refer to the Chatbot Bank Logins page for more details.
  • :beach_umbrella: Client Dashboard (Chargeback Transaction Disputes): Added 222-222-2222 as a test value phone number to use for disputing transactions to avoid real data requirement on sandbox.