The Aura Pro Page Says Two Different Things About Payment. Here's the Actual Sequence.

description: "A working Android AI prompt app for $299.99. The page's How to buy section and its final checkout block describe different payment paths - here is the actual sequence, step by step, from the page itself."

The short version

I was reading the Aura Pro product page to work out what happens after I decide to buy. The page has a "How to buy" section and a separate block right at the bottom of the page, and the two do not describe the same sequence.

I checked both, and then I ran the demo. Here is the actual flow, in order.

Try it yourself: https://reggiebro.github.io/WorkflowAlpha.ai/landing/

---

What the "How to buy" section says

Four steps, each with its own heading:

1. Step 1 — Test the demo APK. Download and install it, open it, type a request in any of the 11 categories, and confirm the prompt generation works.
2. Step 2 — Contact to purchase. Email [e-mail], state you want to buy Aura Pro, and the price and payment details are confirmed.
3. Step 3 — Pay via Western Union or MoneyGram. That is the step heading, verbatim. The body text underneath adds that PayPal and crypto (ETH / USDC / USDT on Base) are also accepted, and that all three routes are accepted.
4. Step 4 — Get the full package. After payment confirmation you receive the complete package as a zip.

So the section reads: test first, email, pay, receive.

---

What the bottom of the page says

The closing block is shorter and goes in a different order:

"To buy: email [e-mail] — we'll confirm payment details and deliver the package after payment. Email is the only contact method. No PayPal, no cards, no escrow."

And directly above it, a separate line:

"Pay with PayPal: send 299.99 USD to [e-mail] — that is our PayPal account. You get a payment request, we confirm it in our inbox."

Read those together and you get a contradiction. Step 3's heading names Western Union / MoneyGram; the closing block says "No PayPal"; the line above the closing block hands you a PayPal address anyway.

I am not going to tell you which one is the typo. I will tell you which one is actionable: the PayPal line has a concrete address and an amount, and the closing block has a flat "no PayPal" with no alternative in that same sentence. One of them is stale copy.

---

What the page is certain about

These parts are consistent across every section, so treat them as the real spec:

• Price: $299.99 USD, one-time. The buy button reads "Get Aura Pro — $299.99 USD", and the sub-line is "One-time payment. Full package. Lifetime ownership."
• Package contents: signed app-release.apk, play_takeover.py, upload_to_play.py, README-TAKOVER.md, README-PLAY-SETUP.md. Optional: aura-release.keystore and the full aura-pro/ source tree.
• Post-payment sequence: you set up the Google Cloud project, enable the Play Android Developer API, create a service account, invite it into Play Console, then run one command. Everything after that is documented.
• Contact: email only. [e-mail].
• Crypto address (Base): 0x078fE079A9440631Bc6AD722D7143dC382b4ea4f — ETH, USDC, USDT.
• Build: "Built with Ionic/Capacitor. Google Play Billing via BillingClient 6.2.0. 11 intent categories. Works offline."

That is the whole deliverable. If you are evaluating this, those eight bullets are the part worth checking against your own expectations.

---

What the demo actually does

I ran it in the browser rather than installing the APK, since the page describes the preview as "the same logic that runs on-device."

11 categories, all wired: Build, Write, Design, Learn, Marketing, Business, Personal, Finance, Legal, Debug, Analysis. Each one is its own template — the page is explicit that generation runs on-device and needs no API key for core generation.

What a generated prompt contains. I picked a category and typed a topic. The output is not a paragraph; it is a structured document with a numbered requirements list and an ## Output Format block naming the sections the model should produce. The topic string appears twice in every template: once in the task sentence and once in the closing instruction.

What it does not do. It does not call a model. I checked the page source for network calls and found none — no fetch, no XMLHttpRequest, no endpoint of any kind. The generator is local JavaScript that interpolates your topic into one of eleven hand-written templates. That is consistent with "works offline", and it means the app's value is the structure of the prompt, not the quality of a response from a model you did not supply.

That last point is the honest framing of this product, and it is worth saying plainly: you are buying a prompt scaffolding tool, not an AI backend. If you expected the app to generate finished marketing copy on its own, the demo will not show you that, because the app does not do that. What it does is hand a model a well-formed brief, which is a different job — and for anyone already paying for a model, arguably the more useful half.

---

Before you pay, test these

The page is right that this is testable first. Concretely:

• Install the demo APK (isDemo=true unlocks every premium feature — no paywall, no API key).
• Run all 11 categories and confirm none of them returns a blank or crashes.
• Confirm the generated prompt is the same structure you saw in the browser preview.

If those three pass, the takeover is one command. If they do not, you have learned that before spending $299.99, which is the entire reason the demo exists.

---

Paying

Listed on the page, in one place or another:

• PayPal — send $299.99 USD to [e-mail]. Add a note saying what you are buying and it is confirmed in the inbox.
• Crypto — 0x078fE079A9440631Bc6AD722D7143dC382b4ea4f on Base (ETH / USDC / USDT).
• Western Union / MoneyGram — payment details sent after you make contact.

To start: email [e-mail] with what you are buying.

The page does not use a paypal.me link for this account, so pay to the email address rather than hunting for a slug — and if the closing block's "No PayPal" line is the accurate one, ask which of the two you should use before you send anything.

---

Bottom line

Aura Pro is a finished Android app with Play billing already wired and a takeover script that does most of the Play Developer API work for you. The demo is real, offline, and genuinely testable before purchase.

The one thing the page gets wrong is its own checkout instructions. Two sections disagree about payment, and neither is marked as the current one. That is a copy bug, not a scam — but it is the kind of thing worth asking the seller to confirm in writing before money moves.

If you've taken over an app on someone else's Play Console, what did the billing wiring actually require? I'm curious whether the "one command" claim survives contact with a real Console.