Step 3 - Handle MFA (if necessary)

Step 3: Handle MFA (if necessary)

Some financial institutions require an additional verification step before returning data. If this occurs, the job status will move to pending_mfa and Aerosync will emit a pending_mfa webhook to your registered endpoint.

For the full handling flow, code sample, and sandbox testing instructions, see MFA Challenges.

Finding your jobId

To re-launch the widget for MFA, you will need the jobId returned in the response from Step 1 when you created the job. Make sure you store this value alongside your connectionId when the job is created.

Detecting pending_mfa

• Webhook (recommended): listen for a webhook with pending_mfa status
• Direct poll (backup): check GET /v2/accounts/{connectionId}/job/{job_id}
  for a jobStatus of Pending MFA

Once the user completes the MFA challenge, you will receive a completed webhook and can proceed to retrieve your data in the next step.