Multiple Accounts are here! (And some API updates)

We’ve recently made a couple of improvements to your Beyonic account, that I’d like to share below:

Web Portal Updates:

For customers using our Web Portal, you’ll be able to take advantage of the following new feature:

Multiple accounts of the same currency

You no longer need to maintain multiple sub organizations just for separating out your internal projects.

Now, you can create an unlimited number of additional accounts to split up funds within your organization. For example, instead of having one UGX currency account, you can have one for internal operations, one for salary payments and another for beneficiary payments. Each account will have its own separate balance and account statement.

You can also specify who can initiate payments from each of those accounts, and request specific authorization procedures for each account.

By using separate accounts instead of separate organizations, your users do not have to remember multiple logins or enter contacts twice. You can share contacts across your various projects.

API Updates

For the customers who use our API, we have added some nifty features:

1) Notification Event Logging

When Beyonic sends a notification to your notification URLs, we now log the request and response for 30 days. This makes it much easier to debug your callback URLs and confirm the IPN formats during integration.

To see your events, simply go into your organization settings (by clicking your organization name in the top right corder of the screen), and then click “Notification Endpoints”

You will need to add at least one notification URL, and then you will see a new column called “Recent Events”. Use this to access any notifications set to that URL

2) Collection Request Information is now included in Collection Notifications

Previously, when we sent the “collection.received” notifications, they only included the collection request Id (if there was a matching collection request). You were required to make an additional API call to retrieve the full collection request information.

Now, the notifications will include the expanded collection request information, so that you don’t have to make that additional API query.

Note 1: This information will only exist if we were able to successfully match an incoming collection to a previously created collection request

Note 2: Since this is a backward incompatible change, you will have to update your API version to V3 or higher in order to access this feature.

As usual, we look forward to hearing your feedback!