Without Beyonic, collecting funds using mobile money is not very user friendly:

  1. Depending on the network, subscribers have to go through 8 – 9 steps on their phones in order to send you money. See the "Per country" section of our collections guide for more information
  2. Subscribers have to remember the Merchant ID and the Reference Code in order correctly send you funds.
  3. Even with lots of training, the multiple steps take long and increase the chance of making mistakes. Customers report over 30% error occurrence.

Beyonic’s collection tools are designed to make collections easier for your users by:

  1. Reducing the number of steps a user has to remember
  2. Automatically detect mistakes made by subscribers and route the funds to you correctly

The majority of errors are due to a missing or wrongly entered reference code. With Beyonic’s collection tools, in many cases, you can eliminate the reference code all together, which reduced the amount of information the subscribers have to remember or enter, and greatly reduces mistakes. Some of the mechanisms for doing this are discussed below:

  1. Using collection requests to request funds from the customer

    Most networks support Beyonic collection request. When you initiate a collection request, all the customer has to do is enter their pin code to confirm a transaction. They do not need to go through 8 or 9 steps to send you funds. You can create a collection request from the Beyonic portal, or using Beyonic's collection requests API.

    Even on networks that don't support the one step PIN entry, when you create a collection request, Beyonic sends instructions to the customer (unless you tell us not to). This reduces errors by letting customers know exactly what to do to send funds to you.

    Lastly, when you create a collection request, any incoming payments are first checked against all pending collection requests in your account. So when a matching collection comes in, it’ll be automatically assigned to you, even if the user forgot to enter the correct descriptions (references).

    Beyonic collection requests are a great way of eliminating user errors. See our Collection Requests API documentation for more information.
  2. Manually "claiming" collections via the collections API (or the Beyonic portal)

    If your customer tells you they sent a payment to you, you can use the Beyonic portal or the collections API to query for the payment using the phone number, amount or transaction id returned by the MNO.

    To do this, you search for the collection, in a similar way to how you'd normally search through your collections (See “Searching for a collection” in our API documentation), but you also include a "claim" parameter that will additionally search unmatched collections as well, and assign them to you if they match the data you are searching for. See “Claiming an un-matched collection”  for more information.

    "Claiming" collections is another way to improve the quality of mobile money collections. It allows you to find your collections even if your customers skip some of the steps or make errors when sending the funds to you.

    With this feature, you might eliminate the use of reference codes all together, and simply claim the collections manually via the API after your subscribers notify you that they have submitted payments to you.
  3. Requesting your own Merchant ID

    With your own Merchant ID, your customers may not have to enter a description or reference code when sending money to you. This means your subscribers only have to remember one piece of information. In addition, you can tailor your merchant ID to be easy to understand within your solution’s context. You will need a Merchant ID for each mobile payment network. Beyonic can assist you with the application process

    Note that Merchant IDs must be requested per mobile network, are subject to availability and may attract setup costs.
  4. Flexible reference code matching

    Beyonic’s reference code matching is powerfully designed to respond to incorrect input.

    First case insensitive, which means it will work even with wrongly capitalized reference codes or descriptions.

    We match the beginning of the subscriber’s entry (not the whole entry), which means any extra data can be included after the reference code (either by mistake or design). This extra data shall be passed on to you via the API’s notification features.

    Lastly, Beyonic’s reference code matching algorithms are able to match even if there are minor errors in the reference code, greatly reducing failed payments.
  5. Manual matching

    If all else fails, Beyonic has a team of support agents who will be notified when a payment is made that cannot be matched. They will attempt to manually match the incoming payments. This may include reaching out to the subscriber or to your organization to confirm the intentions of the payment.
Did this answer your question?