Pick an amount.
Try checkout.

Connect my existing signed-in café app to a hosted Dodo Payments checkout in TEST MODE ONLY. First inspect the current code and read the latest official Dodo integration and testing guides. Use the existing stack; do not switch the whole application to another framework.

On the contribution screen, show four INR presets: ₹500, ₹1,000, ₹2,000 and ₹5,000. Update the on-screen summary when the selection changes. Add an optional display name and a short note, keeping the note with the owner’s contribution history. Do not turn it into a public comment wall. Validate allowed amounts and input limits on both client and server; use integer minor units internally.

Create the hosted checkout from the server using test credentials and product settings appropriate to the current Dodo API. Follow current currency/pricing documentation instead of guessing how INR or a custom amount is configured. Persist a pending contribution with the verified signed-in owner, campaign, amount, currency and note, and associate the provider identifiers with that record. If the backend is shared, preserve the application boundary.

Keep API and webhook secrets server-side. The frontend may redirect only to the genuine checkout URL returned by the provider. Add a clear “Test checkout. No money will be charged.” notice and link to Dodo’s current test-payment guide. Use official test-card guidance, not a real card.

After the visitor returns, show the saved record as pending until the server verifies payment confirmation. A return URL or status query parameter is not proof of payment. Verify the webhook signature against the raw request body; match provider identifiers, currency and amount to the pending record; process repeated events idempotently. Display failed, cancelled and expired states honestly.

Verify the allowed presets, input errors, an actual hosted TEST checkout, pending/confirmed/failed paths, owner isolation and duplicate-event handling. If provider access is missing, complete independent implementation and list the missing setup instead of claiming a payment succeeded.

Official integration guide:
https://docs.dodopayments.com/developer-resources/integration-guide
Official testing guide:
https://docs.dodopayments.com/miscellaneous/testing-process