You now can do even more with Verify, our first-of-its-kind bank account verification solution.

Today, we’re thrilled to announce a third tier of verification, Verify Account Ownership Via Name Match, all available via the same API integration.

With three distinct verification tiers now available, we’ve also made Verify more flexible so you can choose whether to validate bank account status or turn on higher tiers that also validate the control of the bank account or ownership via name match.

To achieve this, a new type of bank account verification field has been added to the Verify API, giving you the option to run tiered Verify requests either independently or simultaneously:

• status_ownership: Verifies the status of a bank account alongside the Account Ownership Via Name Match request
• control_ownership: Verifies the status of a bank account and that the end user has control of the bank account alongside the name match request.

If you don’t have access to Verify and would like to discuss adding the solution or if you have additional questions about the latest enhancements, we’d be happy to chat. You can reach out to our team either by replying to this message or emailing [email protected].

You can now cancel transfers through the portal or through an API request!

Canceling via Portal

From the Transfers page within the Orum Portal, click the new Actions button, select Cancel, and confirm your choice. That’s it! The status of the transfer will update to Failed and display an info icon noting that the transfer was manually canceled.

Canceling via API

Please check out our Cancel API Docs here!

General Notes on Cancellations

• Cancellations cannot be reversed.
• Transfers may only be canceled if they are in “Pending” status. If a transfer is unable to be canceled, the option will be greyed out.
• Canceling an ACH or SDACH transfer will only succeed if the transfer has not yet been submitted for processing (see cutoff times for more details).
• For A2A transfers, the credit leg may be canceled regardless of the payment method (RTP, FedNow, ACH, or SDACH) if the credit leg has not yet been submitted.
• Only users with Admin or Payment Initiator roles are enabled to cancel transfers.
  
  

You can now do even more with Verify from the Orum Portal. Our new enhancements make it easy for you to Verify Account Status of individual bank accounts with a few simple clicks — giving your operations more flexibility and efficiency to handle one-off Account Status verifications.

Here are the details:

From the Verify page within the Orum Portal, click the + Verify Account button, fill in the information, and then Verify Account. That’s it — the results will appear as a new row in the Verify Details table.

It’s important to note that only users with Admin or Payment Initiator roles are enabled to use this new feature.

When creating an external account, we have now added a synchronous validation check to ensure that the routing number that is being passed is a valid routing number.

If the routing number is not valid, we fail the creation of the account and send an error message as shown below:

{
 "error_code": "invalid_routing_number",
 "message": "Routing number is invalid. Pass a valid 9-digit routing number."
}

You can now initiate single leg payments directly through the Orum Portal! See below for a breakdown of the newly available feature.

Top Ups to your FBO

You can now top up your FBO balance directly through the portal. Simply log in to the Orum Portal and visit the "Balance" page. You should see a "Top up balance" button in the top right as below:

Next, click the button and select an enterprise account. If your enterprise does not have an associated enterprise account in Verified status, then you can create one directly through the modal.

Lastly, fill out your top-up details and initiate! You will be able to track the status of the initiated transfer in the Transfers table as per usual.

Debits & Credits to/from a single Person or Business

You may also initiate a debit from a single person/business, or credit a single person/business. To initiate a payment to a person/business, first visit their details page in the portal. Ex: see a Persons details page below:

Next, locate the account to which you'd like to send/receive money from, and select the new "Transfer Money" option underneath the Actions menu of their associated accounts:

Then, fill out your transfer details and initiate! You will be able to track the status of the initiated transfer in the Transfers table as per usual.

Note: Only users with Admin or Payment Initiator roles will be able to view and use the payment initiation feature.

Please reach out to Orum Support with any questions or feedback. We're super excited to get this in your hands!

We've made two major updates to our authentication flow - please see below!

1. Removal of API Keys

From now onwards, you will no longer need to manage two sets of API Keys & API Credentials to authenticate to our APIs. Instead, you will only need to manage a set of API Credentials.

All API calls now have the field x-api-key as optional, and only API Credentials are necessary to authenticate moving forward.

2. Updated Auth Endpoint

We have released a new auth endpoint (/oauth/token) that adheres to the standard OAuth2 spec. With this update, you can now use off the shelf OAuth2 clients for your integrations! Some examples below:

• Node.js: simple-oauth2
• Go: golang.org/x/oauth2
• Python: oauthlib
• Java: spring-security-oauth

Lastly, in order to use the new endpoint, you must create a new set of API Credentials through the Orum Portal.

IMP: All credentials created through the Orum Portal from this point forward can only be used with the new /oauth/token endpoint.

Previous Endpoint & Credential Deprecation Plan

We will continue to support the deprecated /authenticate and /refresh endpoints along with all previously created API Credentials. However, the functionality to rotate any existing credentials will be removed from the Orum Portal. If you must rotate any existing credentials, please reach out to Orum Support.

We will urge all existing customers to migrate to the new endpoint by January 15, 2025, and will support the deprecated endpoints and credentials until then.

Introducing a new way to access all of the benefits of our Verify product without having to write a line of code!

Users can now verify accounts in bulk by simply uploading a CSV containing all account details and instantly access verification results.

This new feature is available in the Verify tab in the portal under the new "Verify Initiations" tab - as seen below!

Now, you can add a Person, Business, or Account directly through the Orum Portal!

To add Persons & Businesses, please navigate to the "Persons" or "Businesses" page in the Orum portal and select the "+ New Person" or "+ New Business" button in the top right corner.

To add Accounts, please select a Person or Business from the table, and scroll down to select "+ New Account" to create an account that is associate to that Person or Business.

Note: Only portal users with the Admin or Payment Initiator roles will be able to access this feature.

Orum customers will now be able to determine if an account is debitable, and if not - if it is due to a debit block. Orum’s debit block detection enables customers to determine whether or not a debit block has been placed on an account. The goal of this functionality is to inform you when there is an account that cannot be debited, so that you can inform your end users that an action is required in order to make the account debitable.

Transfer Groups are now available! We have recently added Transfer Group APIs to allow for grouping together any set of transfers that may be associated with the same flow.

To create a transfer group, you must specify the ultimate source or destination of the group. Once specified, a group will be created, and you can attach the generated unique ID when creating all applicable transfers moving forward. Please see the updated Transfers request body.

Additionally, you may also search for all transfers associated with a transfer group by specifying the unique ID as a query parameter in the Get Transfer API.