Ensure an end user has control of the bank account.
Orum verifies account control by sending a unique four-character code to the bank account of your end user and prompts them to authenticate it — removing the lost time and expense of microdeposits.
The maximum number of attempts an end-user can enter the code defaults to three.
Once the end user locates the code within online banking, there are two ways to confirm it:
A control verification also includes an account status verification. This means both control_status
and verification_status
will update to valid
upon success.
If you prefer owning the entire user experience with your brand, this is the option for you. In this option, Orum still sends a penny with a unique 4-character code to the end-user’s bank account. However, the rest of the experience is managed by you, the enterprise.
Here’s how it works:
This approach works best if you want the process to be a natural extension of your brand, since you are in control of how you communicate with the end-user and the experience they’ll have submitting the code.
If you don’t have the resources in place to build your own user experience, our hosted email solution could be a great fit.
Here’s how it works:
Example Email
Delivered from your domain but sent by Orum
This approach works best if you are comfortable with a generic branding experience and don’t have the resources or systems in place to send emails or build and manage the code-acceptance experience.
If using the email-based solution, Orum will send an email based on the following logic:
verify_account_updated webhook
event returns a verification_status
of valid
.Follow the below steps to enable Orum to send emails on your behalf securely and reliably. This process ensures your emails are trusted by recipients and aren’t marked as spam.
After the above steps are completed, Orum will:
Regardless of whether you choose to use the API-based or email-based solution, the Control statuses and webhook events remain the same.
Ownership Status | Description |
---|---|
Pending | Acknowledgment of the request being received |
Valid | A match has occurred and ownership has been verified |
Canceled | The maximum number of attempts has been reached, a transfer has failed, or it has been 5 days since the request was sent to the receiving bank |
You will be blocked from making >5 verification requests to the same account within a 24 hour period.
Ensure an end user has control of the bank account.
Orum verifies account control by sending a unique four-character code to the bank account of your end user and prompts them to authenticate it — removing the lost time and expense of microdeposits.
The maximum number of attempts an end-user can enter the code defaults to three.
Once the end user locates the code within online banking, there are two ways to confirm it:
A control verification also includes an account status verification. This means both control_status
and verification_status
will update to valid
upon success.
If you prefer owning the entire user experience with your brand, this is the option for you. In this option, Orum still sends a penny with a unique 4-character code to the end-user’s bank account. However, the rest of the experience is managed by you, the enterprise.
Here’s how it works:
This approach works best if you want the process to be a natural extension of your brand, since you are in control of how you communicate with the end-user and the experience they’ll have submitting the code.
If you don’t have the resources in place to build your own user experience, our hosted email solution could be a great fit.
Here’s how it works:
Example Email
Delivered from your domain but sent by Orum
This approach works best if you are comfortable with a generic branding experience and don’t have the resources or systems in place to send emails or build and manage the code-acceptance experience.
If using the email-based solution, Orum will send an email based on the following logic:
verify_account_updated webhook
event returns a verification_status
of valid
.Follow the below steps to enable Orum to send emails on your behalf securely and reliably. This process ensures your emails are trusted by recipients and aren’t marked as spam.
After the above steps are completed, Orum will:
Regardless of whether you choose to use the API-based or email-based solution, the Control statuses and webhook events remain the same.
Ownership Status | Description |
---|---|
Pending | Acknowledgment of the request being received |
Valid | A match has occurred and ownership has been verified |
Canceled | The maximum number of attempts has been reached, a transfer has failed, or it has been 5 days since the request was sent to the receiving bank |
You will be blocked from making >5 verification requests to the same account within a 24 hour period.