Security
Your customer stays in control.
The intended JujeePay journey sends the customer to their own bank to review and authorise a payment.
Designed around customer authorisation
Customers should approve payments through their bank’s own experience. They should never share their bank password with the merchant, and JujeePay is not designed to ask for it.
Payment requests keep the merchant, amount and reference visible so the customer can review what they are paying before authorising.
Early-stage product
JujeePay is in development. The payment flows shown in this prototype are simulated, no money moves, and production connectivity to a regulated payment provider is still required.
We do not claim FCA authorisation, bank partnerships, certifications or live Open Banking connectivity.