Built on HRUM
A consultation app built on HRUM
From the consultation screen to payments, refunds and payouts: we open up an app that really runs on HRUM.
The payment screens below are our own internal test (QA) orders. They are not real customer payments — they record us paying and cancelling along the same path ourselves.
Get started with HRUM Follow along
Case study — Miho Saju
Saju consultations with Miho the nine-tailed fox, who remembers you
Miho Saju is a web app that shows your Manseryeok (the Korean Four Pillars calendar) chart from your birth date and lets you talk through your Saju (Four Pillars of Destiny) with a character named Miho. It remembers past conversations and picks up where you left off, and it can also check two people's compatibility.
The app's operator didn't buy servers or sign a separate contract with a payment company. They used these four things from HRUM.
-
Saju and consultation APIs
Manseryeok, Saju readings, consultations that remember the conversation, and compatibility all come from the HRUM API. The app server holds the HRUM key and makes the calls; the key never reaches the screen.
-
App hosting
Connect a GitHub repository and HRUM builds, deploys and opens the app at its own address. That's how Miho Saju is hosted too.
The payment screens below are our own internal test (QA) orders. They are not real customer payments — they record us paying and cancelling along the same path ourselves.
-
HRUM Payments (Toss Payments checkout)
When a customer taps "Buy" in the app, HRUM creates the order and the Toss Payments card checkout opens on the HRUM Payments page. After paying, the customer returns to the app's result screen. The price comes from the product registered on HRUM, not from the app, so it can't be tampered with on the screen.
-
Cancellations, refunds and the payout ledger
When a payment is cancelled, the sale, fee and refund are all recorded in the HRUM ledger. Sellers can see on the payouts screen what came in and what went out, and sales past the holding period are scheduled to be paid to the registered account on the set payout date.
Follow along — from consultation app to getting paid
-
Sign up for HRUM and get an API key.
Create a key in the console and keep it on your app server only.
-
Build the consultation screen.
For readings like Saju, tarot and compatibility, just call the HRUM API. If code is a hurdle, you can build it with the mouse in Baro, our block-based app builder.
-
Put the app online.
Connect your GitHub repository to HRUM app hosting and your app gets its own address.
-
Register what you sell.
After completing seller registration, register the product name and price on HRUM.
-
Wire up the "Buy" button.
Your app server requests a payment from HRUM and sends the customer to the HRUM Payments page — that's it. The app confirms the result by asking HRUM again.
-
Check the payouts screen.
Sales, fees and cancellations build up in the ledger, and payouts go to your registered account on the set payout date.
To be upfront
- The payment and cancellation screens on this page are test orders the HRUM team paid for and cancelled right away. They are not records of real customer payments.
- Miho Saju is an example app built by the HRUM team. We'll add real cases from outside consultants to this page as they give their consent.
Start your consultation app on HRUM
Sign up to create an API key right away, then use app hosting and HRUM Payments from the same console.
Contact: contact@float.do · Operated by FLOAT Co., Ltd.