Waffo Pancake
MeDo supports Waffo Pancake, so your AI-generated app can take one-time payments and subscriptions through your own Waffo account, with Waffo handling sales tax as the merchant of record.
Your app can take payments through Waffo Pancake. Waffo is the merchant of record: it appears as the seller on the buyer's receipt, is responsible for sales tax, emails the receipt to the buyer, and pays the money out to your Waffo account. MeDo never holds it. This is separate from what you pay MeDo for credits.
Before you start
- A Waffo Pancake account with a store. Sign up at the Waffo Pancake dashboard and create your store there. MeDo does not create a store for you.
- Your Merchant ID and an API private key from that dashboard.
- Sign-in on your app. Subscriptions always need sign-in, because the membership has to belong to an account. For one-time payments sign-in is recommended: each order belongs to the buyer's account and shows up in their order history. An app without sign-in takes guest one-time payments; guests have no order history, and refunds for those apps are made in your Waffo dashboard. See Managing sign-in & users.
- A backend, since orders need somewhere to live. See Backend settings & keep-alive.
- Publish before taking real money. See Publishing a release.
- Credentials are not copied with an app. A copied app needs its own Waffo configuration from its owner.
What you can do
- Accept one-time payments on a Waffo-hosted checkout page, paid by card, digital wallet or a local payment method
- Sell subscriptions billed weekly, monthly, quarterly or yearly; members can cancel, and keep access until the end of the period they paid for
- Show buyers their order history and members their renewal date
- Issue full refunds of one-time orders from an admin page inside your app, within 14 days of the payment
- Charge the price you list: prices are tax-inclusive. Buyers who pay in another currency see Waffo's converted amount
- Let members manage their billing in Waffo's customer portal (payment method, invoices), linked from the membership page
Example query:
“Build a membership site with a monthly plan and two digital downloads, and take payments with Waffo Pancake.”
Note: Partial refunds, refunds of subscription payments from inside the app, switching between plans, free trials and usage-based billing are not supported. Each app sells in one currency: US dollars unless you ask for euros, pounds, Hong Kong dollars or yen, and each payment must be within Waffo's range for that currency (1 to 10,000 US dollars). Refunds are an admin-only action inside the app; apps without sign-in have no administrator, so refund those payments in your Waffo dashboard.
Add Waffo Pancake to your app
MeDo reaches for Stripe by default, so name Waffo explicitly. Either ask in the conversation —
"I want to accept payments with Waffo Pancake in my app."
— or type @ in the prompt box, pick Waffo Pancake from the Skill list, and describe what you are selling in the same message.
Each app uses one payment provider. Once the app includes Waffo Pancake, MeDo asks you to configure your credentials before checkout will work.
Configure your credentials
Click the configure button at the end of MeDo's reply, or open the Skill view in the editor's left rail and choose the Waffo Pancake card. Then:
- Open the configuration dialog.
- Open the Waffo Pancake dashboard and sign in.
- Go to API & Development.
- Copy your Merchant ID. It starts with
MER_. It is not the Store ID. - Under Create an API Key, choose Test Mode or Live Mode (see the next section) and click Create Key.
- Copy the private key. Waffo shows it only once, so copy it before closing the window.
- Return to MeDo's dialog, paste both values into the corresponding fields, and submit the form.
Paste the private key exactly as Waffo gives it to you — one long line. A key in PEM form (with -----BEGIN PRIVATE KEY----- lines) also works. MeDo checks the two values with Waffo before saving them. If that fails, make sure the Merchant ID and the key come from the same Waffo account and that the whole key was copied, then try again.
Then open checkout in your app (sign in first if it has sign-in). The buy buttons become active once the app has confirmed your credentials. If they stay disabled, re-check the configuration and reload.
Credentials are masked when displayed again. Never paste the private key into page content or ask MeDo to put it in the code. See Keys & data safety.
Test mode vs live mode
A Waffo API key belongs to either test mode or live mode, chosen when you create the key. The generated app uses whichever key you saved; you do not enter a separate environment setting.
In test mode, the checkout page says that no real payment is processed, and the app marks those orders as test payments.
What Waffo's review needs: your published app reachable without signing in, prices visible before checkout, Terms and Privacy pages, a support email shown on the site, and that email and your app's domain verified in the Waffo dashboard. The review usually takes one to three business days. You can ask MeDo to add the Terms and Privacy pages, the support email and Waffo's domain verification tag.
Switching from test to live: after your store passes Waffo's review, create a Live Mode key in the same place, then save the Merchant ID and the new private key together in the same Skill configuration form. Test and live are separate at Waffo: orders and memberships made with the test key stay in the app as test records and are no longer updated, so a tester who subscribed in test mode subscribes again in live mode.
Note: If a published app still uses a test key, visitors cannot pay for real. Switch to a live key before you start selling.
If a payment is still processing
The checkout page opens in a new tab. After paying, the buyer returns to your app by pressing Done on Waffo's page; the app also checks by itself on the page where the purchase started and whenever the order history opens, so a buyer who simply closes the tab is still picked up. The return itself never counts as proof of payment. Buyers type their own email on the checkout page, and Waffo sends the receipt there.
- Still pending: use the check-status action on the result page or open the order in the order history, rather than paying twice. While the checkout page is still valid, the app links back to it so the buyer can finish the same payment. Checkout pages expire after 24 hours.
- Declined: a declined payment closes that checkout page. The order shows as not completed, and the buyer starts a new checkout.
- Refunds take a moment: after an administrator requests a refund, the order shows Refund processing until Waffo reports it as refunded. Reopening the admin orders page re-checks it.
- Renewals: the app picks up a renewal, a failed renewal, or a change the member made in Waffo's customer portal the next time the member opens the app. If a renewal payment fails, Waffo retries it and the member keeps access for about a day.
MeDo does not reconcile in the background after the buyer leaves, and a refund you make directly in the Waffo dashboard is not copied back into the app. Compare any unresolved order against the transactions in your Waffo dashboard.
After setup
Once your Waffo configuration is complete:
- Payments from your app are collected by Waffo and paid out to your Waffo account.
- You can view orders, subscriptions, payouts and tax details in your Waffo dashboard.
- Full refunds are issued by the app administrator through the admin refund action inside your app; for apps without sign-in, refund in your Waffo dashboard.
- Waffo charges its own fees according to Waffo's terms.