Skip to main content

Flash Connect: Enhanced sub-client status visibility

Support avatar
Written by Support
Updated over a week ago

Flash Connect now provides improved visibility into a sub-client's (aka Virtual Account Number, VAN) current status. This enhancement is designed to reduce uncertainty caused by the occasional manual review process required for some sub-clients.

We have expanded the list of possible sub-client statuses from two to six to give you more granular visibility and clarity on the sub-client's lifecycle.

Previous Statuses

  • ACTIVE

  • DEACTIVATED

New Statuses

  • INITIATED
    The sub-client has been created and is currently undergoing automatic compliance checks.

  • ACTIVE
    The sub-client is fully activated and approved. You can deactivate it.

  • UNAPPROVED
    The sub-client is pending manual compliance review.

  • DEACTIVATED
    Can be activated by you at any time.

  • FAILED_KYC
    The sub-client has failed KYC checks and is blocked.

  • DISABLED
    The sub-client has been permanently blocked and cannot be used for transactions.

New Webhook Events

A set of new webhook events is now available. A webhook is sent every time a sub-client's status changes, allowing your system to react instantly to changes in the sub-client lifecycle. See our Webhook Documentation for details on the new events and their payloads.

How to Subscribe to Sub-client Status Webhooks

Clients can now subscribe to new sub-client status change events directly through the Flash Connect UI, ensuring immediate notification of any lifecycle updates.

  1. Navigate to Webhooks: Go to Flash Connect → Webhooks.

  2. Create or edit a Webhook: Click the “ADD WEBHOOK” button to create a new webhook, or select an existing one to modify.

  3. Configure Subscription: In the modal window that appears:
    - Select the webhook category "subclient" from the left-hand panel.
    - Check all the necessary status boxes to subscribe to the sub-client status events you require.
    - Provide the link to your receiving endpoint.

  4. Save Settings: Click the “Save” button to finalise the webhook settings.

Did this answer your question?