Pre-Launch Checklist | Parallel Developer Documentation

Version: Current – v2.x

General Items

  1. Make sure folks on 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. See the response parameters section in the Case Management record docs for more info.
  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). You can also see the details around the access expiration in the Case Management API.
  5. If you'd like to keep a user's identity, profile, or accreditation data up to date, ensure you are listening to webhooks rather than polling the API. If you are listening to webhooks, ensure you return a 200 response within 5 seconds.

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).