Release Notes
Back to All
added

Release 3-31-25

16 days ago by [email protected]

Hello partners! Please read below to learn about the most recent additions, removals, and changes to our API documentation in March 2025. Highlights include Joint Accounts and a new Socure SDK Integration for the Enrollment process.

High Level Overview

Added

  • Joint Accounts API & API Guide
    • The "Create Joint Account API" allows partners to change an individual account to become a joint account.
    • Webhooks were also added for APIs affected by Joint Accounts.
  • Socure SDK Integration is now live
    • We at GD have updated our IDV and CIP processes. This will affect the enrollment process and requires a new SDK integration from Socure. Read on below for more info.

Changed

  • Some existing APIs are now affected by Joint Accounts and have been updated in the respective API guides.

Added

Joint Accounts API & API Guide

  • The Joint Accounts API guide is now available, including the new Create Joint Account API that allows partners to change an individual account to become a joint account.
  • This also has many implications for other APIs that relate to the Joint Account feature, that can be found in the "Changed" section below.
  • Joint Account Webhooks have also been added to the Webhooks page for these affected APIs.

Socure SDK Integration

📘

We at GD have updated our IDV and CIP processes. This will affect the enrollment process and requires a new SDK integration from Socure.

A user may need to verify their identity in certain situations, including:

  • Enrollment: If we cannot establish a user's identity, we must validate it using official identity documents.
  • Suspicious Activity: Following enrollment, if any suspicious activity is detected on the user's account, it may be temporarily locked until identity documents are verified.

To validate a user's identity, we employ the Socure Doc V SDK. Users must upload their ID documents along with a live selfie to complete the identity verification process. This information will be analyzed to ensure successful verification.

  • For IDV workflow, the Socure SDK needs to be integrated within a partner's website and mobile apps. With Socure SDK, customers will be redirected to a Socure-enabled page where they can upload both the front and back images of their ID documents along with a selfie in real-time using their smartphones. Once the documents are successfully uploaded, that SDK will generate a unique document ID, which will then be used to validate users' identity.
  • For CIP, there won't be any changes from the customer's perspective, except for the optional step of capturing the customer’s consent to search their SSN record against the public SSA repository. This step is up to partner preference.

For a more in-depth overview, refer to the Socure SDK Integration guide.

For more technical guides, refer to these links on the iOS Socure SDK, Android Socure SDK, or Web Socure SDK.

Also available is information on Callback Methods related to the Socure SDK Integration.

Changed

APIs Affected by Joint Accounts

The following APIs are affected by Joint Account Scenarios: