Who is Judopay?

Judopay is the leading mobile payments platform. Born out of the frustration with friction-fill checkouts, we built a flexible solution designed to securely drive sales and improve the customer experience.

Now wholly owned by Fabrick S.p.A., part of the Banca Sella Group, Judopay is continually building ways to enhance the overall payment experience for businesses and consumers alike.

Available across multiple sectors, our solution is used by KFC, Uber subsidiary Autocab, PaybyPhone, Sigma Sports, Bupa, Hiscox, Foxtons and many more.

What was the problem Judopay was facing before Archbee?

The main requirement for our developer documentation for a while has been to utilise the tabbed way of displaying code snippets, including using tabbed output to organise and consolidate integration steps.

Following the lack of a suitable feature in our current solution, we decided it was prudent to investigate other solutions that could help us to achieve this, including seeing what other features were readily available that were on our wish list.

Why Archbee over the alternatives?

Using markdown files to create our end user documentation was the biggest learning curve, so we needed to have a quick and easy transition to working in this way. An intuitive and user-friendly editor, with easy-to-follow guides, enabled a good proof of concept to begin with, whilst we were trialling out alternative solutions.

We had some requirements that needed to be met with the new solution. For example, the ability to re-use content was very important, tabbed output was a must have as already mentioned, and the ability to easily access files to customise / format our content to align with our brand guidelines needed to have some degree of flexibility.

Archbee was able to provide all these, whereas other alternatives did not, or did not meet the level we required.

Updating and reviewing content was also more aligned with how our developers currently work, so that would be an easy addition to our current change request process.

What are some of the business results you have seen?

Implementing the tabbed code output has been a dream! It was so easy to achieve what we wanted. We also use the tabbed output to switch between steps for each integration type, meaning the topic pages look straightforward and less cluttered. Our end users can get to the integration type they require easily.

Other ‘out of the box’ features which have been instrumental to our improved look and feel is the dark / light theme switcher and the ‘was this page helpful’ topic analytics.

I would also like to highlight the prompt support we have received not only during our proof-of-concept phase, but also since going live – it is reassuring.

Our developer documentation now has a more professional look and is easier for our end users to follow the steps to integrate with us.

We look forward to using more of the markdown blocks to find improved output styles to display our documentation.

‍