Pre-Launch Checklist | Parallel Developer Documentation

Introduction

This is unreleased documentation for Parallel Developer Documentation Next 🚧 version.

For up-to-date documentation, see the latest version (Current – v2.x).

Version: Next 🚧

General Items

Before launching a JavaScript frontend integration in production, there are a few things you should check to ensure you're ready for going live with users.

  1. Make sure members of your engineering/product team sign up for our Parallel Developer Updates mailing list (it can be found on the API landing page).
  2. Ensure you can handle both the case of a user sharing their personal information as well as the case of a user sharing a business' information.
  3. It's possible that a user may decline to consent to share information (we need to ask to comply with numerous privacy laws). While this is a rare occurrence, it's one that is possible.
  4. If an admin at your organization removes access to a user or business from the Parallel dashboard, or if a user decides to stop sharing information, we will notify you (via email and webhooks).
  5. If you'd like to make ongoing server based API requests to access or update information going forward, you should store the unique Parallel ID available via getProfile() at the end of the flow on your backend. The Parallel ID for the subject (individual or business) that completed the flow is necessary to reference that subject's data in the Server API. Alternatively, if an External ID has been set for a record, this value can be used to query the API instead of the Parallel ID.

Accreditation

A user or business may indicate that they don't meet the requirements for accreditation (this will be shown in the indicated_unaccredited_at field). You should make sure you show the user appropriate messaging in this case and, if you believe they could/should meet the requirements, you can tell the user they can submit an application at any time at app.parallelmarkets.com/accreditation.

Caution: You should not initiate another Parallel flow if the user has indicated they are not accredited, because we will not start a fresh application (instead, we re-use the assertion that the user is not accredited and immediately send the user back to your interface).

Identity

For accreditation details, users can share their own individual information or the information for a business they control. For identity (KYC/AML) data, a user can additionally share information on-behalf-of another individual.