Built This Way: Revenue Streams

When building products, it’s an incredible feeling to see them solve the problems they set out to solve. What can also happen though, is your products solving problems you weren’t even aware existed, just due to the way your products are inherently built. We’ve seen this happen at Revenew multiple times, so we want to shed a light on what you get when using Revenew, just because it’s built that way. A note: All Revenew product images you’ll find in this post are reproduced using our fictitious beer marketplace Brewvolution.

One of our customers approached us because they couldn’t find a particular payment in their platform payments. To elaborate, at Revenew we distinguish between platform payments, ie. embedded payments, that are made on behalf of a customer (eg. an Uber driver or an Airbnb host) and direct payments, ie. payments where money moves straight to the platform (eg. for a subscription).

We helped our platform customer identify the missing payment using the payment ID provided by their PSP and found it, but it was not associated with any customer, meaning the customer (recipient in the image below) never got the money for this payment, as it went straight to the platform:

We made the platform aware of this and they clarified that these payments should have indeed been split with a customer.

To make sure this was an isolated incident, we then filtered all payments by their revenue stream and noticed that the opposite was true:

Multiple payments (42 as seen above) had been mishandled and were in need of correction, to view which particular payments were affected, we jumped into the payments view:

With this list of affected payments, the platform was now able to refund customers that should have received money. Luckily, none of them had reached out yet, so the issue was found before it caused customer frustration.

Because Revenew was able to point out all faulty payments, the platform was also able to identify the root cause of the misconfiguration of their payments: They had recently launched a payment links product, where customer fees had not been applied. The platform was able to change the configuration and now all payment link payments go through as expected.