Context
Oen offers a payment platform with CRM, fundraising, memberships, events, and the commerce that runs on top of them. Payment is the layer underneath all of it, and the foundation for all services.
Businesses that come to the API come for flexibility — their own product surface, their own rules about when money moves, everything above the transaction built themselves. PayBeam sits at the other end, for businesses that are already on Oen and want a more flexible way to collect payments.
My role
I led design on both products. For Oen Payment, the work was the hosted checkout (the page a business sends payers to instead of building its own payment form) and the transaction details in the admin panel that comes with the API.
For Oen PayBeam, it was end to end: the link builder and its settings in the CRM, and the checkout the payer lands on under the business's own domain.
Oen Payment
Oen Payment is the payment core sold on its own. A business integrates the API into whatever it has already built, and money moves without any of that running on Oen. What it gets back is the processing and an admin panel to manage transactions against it.
The design question was what to do about checkout. A business integrating an API can build its own payment form. Some want to; most do not. The hosted checkout is for them: the payer leaves the business's site, pays on an Oen page, and returns.
Oen PayBeam
Oen PayBeam runs the other way: no integration, storefront, or catalog. A business on the platform creates a dedicated link, sends it, and gets paid.
Two surfaces hold it up. In the CRM, a settings panel where the business creates and edits a link — what it charges for, and controls like password protection for a link that should not open for whoever it gets forwarded to. On the payer's end, a checkout served under the business's own domain, so a link arriving in an inbox reads as coming from the business rather than from a processor the payer has never heard of.
Impact
- Oen Payment became a major B2B revenue line by volume
- Oen PayBeam filled a gap in the platform: a business can take a one-off fee, a class payment, or a registration without setting up a storefront
Credit
- Design: YuCheng Kuo, Sandy Man, Julia Chan
- Product: Hsiyuan Chou, Elsa Yeh, Nyo Fang
- Engineering: Trista Wei, Calvin Chang, Kelly Pan, Rong Lin, Charlie Chang
- QA: Zion Yu