Case study · Banking and payments

Ezepay

A messaging app with bots that move money.

Client
Ezepay
Service
Design and development
Sector
Banking and payments
Platforms
Web and mobile
Ezepay web dashboard listing merchant payment requests beside the mobile conversation view

At a glance

What happens in the thread

In-chatno separate checkout

Payments are completed inside the conversation rather than handed off to a payment page.

2payment types

Subscriptions and one time payments, both configured by the business.

Botsdoing the work

Intelligent bots facilitate the transaction rather than a human handling each request.

Massivelyscalable

Built for message volume, because a payments channel is only useful if it never queues.

The brief

The checkout is where the conversation dies

A business talking to a customer in a messaging thread has their full attention. The moment money is involved, that thread hands off to a payment page, an app switch, a login — and a meaningful share of customers do not come back.

Which is a strange place to lose people, because everything needed to complete the transaction was already established in the conversation: who they are, what they want, what it costs. The handoff exists for the business's convenience, not the customer's.

Everything needed to take the payment was already in the thread. The checkout was the only thing that left it.

The build

Scale is the requirement, not a boast

Massively scalable is doing real work in the description of this product. A messaging app that also moves money has two load profiles stacked on each other: conversational traffic, which is constant and chatty, and financial transactions, which cannot be dropped, delayed or duplicated.

The bots are where those meet. An intelligent bot facilitating a transaction inside a conversation has to hold the state of both — where the discussion has got to, and where the payment has got to — and reconcile them when either side stalls.

Wow Labz delivered design and development across web and mobile.

What businesses can do

Configure once, run in conversation

Subscriptions and one-off payments

Businesses configure and receive both, so recurring billing and a single purchase use the same channel rather than separate systems.

Product information in place

Sharing what is being sold happens in the same thread as selling it, so a question does not break the flow.

Automated workflows

Businesses set up workflows for a wide range of scenarios, which is what turns bots from an answering service into an operational tool.

Stack

What it was built with

  • Messaging
  • Payment bots
  • Subscriptions
  • Web and mobile
  • Workflow automation

Questions

Ezepay, answered

What is Ezepay?

A massively scalable messaging app with intelligent bots capable of facilitating financial transactions inside the conversation.

What can a business do with it?

Configure and receive subscription payments and one time payments, share product information, and set up workflows for a wide range of automated scenarios.

Why does taking payment in the conversation matter?

Because the handoff to a separate checkout is where customers drop out, even though everything needed to complete the transaction was already established in the thread.

What did Wow Labz build?

Design and development of the web and mobile applications.

Let's talk

Got a developer product nobody finishes integrating?

Tell us what you are building. We will tell you how we would ship it.

Your Multi-Agent
AI Development Crew

Ship production-ready software with
specialized AI agents working together.
exit-cta-img-wowlabz

Let's talk