Next step · What to do next

Add online payments safely

What you may see

I want customers to pay on my site

Why this step

Money code must be written once, carefully: totals on the server, the gateway's page for card details, verified confirmation, and tests before any real payment.

Before you start

Do you have an approved gateway account (and which payment methods does it include)?
Who handles refunds and who sees the payments?

The prompt for this step

What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.

Any error or warning you see now

What you have now (tool, framework, where it is hosted)

Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.

Prompt language

You are a senior engineer and careful product advisor who builds small business websites and apps, and explains every step to people who are not developers. I am not a developer, so explain every step in plain words and tell me exactly which button, menu or command you mean. If you are not sure about something, say so; do not guess.

WHAT I WANT NEXT
Add online payments safely

ANY ERROR OR WARNING I SEE NOW (write "none" if there is none)
[paste the exact error here]

WHAT I HAVE NOW (the tool I used, the framework, where it is hosted)
[write in a few words what you did before it happened]

WHY THIS STEP
Money code must be written once, carefully: totals on the server, the gateway's page for card details, verified confirmation, and tests before any real payment.

DO THESE STEPS, IN THIS ORDER
1. Read the gateway's official documentation and summarise the flow in plain steps (create payment, customer pays on the gateway page, return page, confirmation). Mark anything you could not verify.
2. Build it so the server computes the total from ids and quantities, creates a unique payment per order, redirects to the gateway, and never touches card details.
3. Confirm the payment on the server by asking the gateway for the final status (not by trusting the return page), safe to repeat, and mark the order paid once.
4. Handle failed, cancelled and unclear payments with clear messages, a retry, and a staff list of payments to re-check.
5. Add refunds as a staff-only action with an audit record, receipts, and tests in test mode; give me a go-live checklist.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- In test mode a payment completes, a failed one is handled, a refund works, and amounts match to the fils.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not use real money or real customers while testing.
- Do not put secret keys in the browser.
- Anything I did not ask about: the design, the text, other pages, other settings or the data.
- Do not delete files, data or branches, do not reset or force-push, and do not rewrite history, unless you first show me exactly what would be lost and I say yes.
- Do not paste, print or ask me to paste a password or secret key into this chat. If one is needed, tell me which settings page of the right service to store it in.

WHEN YOU FINISH
Explain in simple words what you changed (file by file or setting by setting), why you changed it, and how I can undo it.

Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.

After you tried it, did it work?

Steps

Read the gateway's official documentation and summarise the flow in plain steps (create payment, customer pays on the gateway page, return page, confirmation). Mark anything you could not verify.
Build it so the server computes the total from ids and quantities, creates a unique payment per order, redirects to the gateway, and never touches card details.
Confirm the payment on the server by asking the gateway for the final status (not by trusting the return page), safe to repeat, and mark the order paid once.
Handle failed, cancelled and unclear payments with clear messages, a retry, and a staff list of payments to re-check.
Add refunds as a staff-only action with an audit record, receipts, and tests in test mode; give me a go-live checklist.

Do not do this

Do not launch payments without a test refund.
Do not use real money or real customers while testing.
Do not put secret keys in the browser.

Try another entry