What is stored
- A random visitor id, in a cookie, so this browser can see the payments it started. It names nobody.
- Your email address and an opaque identifier. Signing in through iamlukia.com gives this demo your email address and an opaque identifier. The demo also keeps a token that lets it ask iamlukia.com, every 15 minutes, whether you are still allowed in; it ends your session if you are not. No password is kept or seen here.
- Your email address, when you ask for your payments by link, with a hash of the link we email you. The link works for 15 minutes.
- Your signed-in devices: for each session, the browser name your browser sends (its user agent), when it signed in and when it was last active. Never a place or a network address.
- Each sandbox payment: amount, item name, reference, method and status, and the provider's notifications about it. Those notifications carry whatever name and email you typed into the provider's sandbox page, and the network address they were sent from.
- On the simulated card page, a test card's last four digits and the test results: never the number, the expiry or the CVV.
- In real mode, what you set up as a merchant: your trading name and VAT number if you give them, a receipt address, checkout wording and logo, payment links and recurring agreements, a notify URL with its signing secret (encrypted), reconciliation runs, the bank account you tell us PayFast pays you into (its bank, holder, type and last four digits: never the whole account number), and an audit trail of what you changed.
- Receipts: the address each one was sent to.
What is never stored
No card number reaches this server.
Nor a password, which is typed at iamlukia.com and never here, or a link we email in readable form. No analytics and no advertising: this server sets no cookie for anything but the ones listed below.
How long
Payments, their notifications and the links that showed them to you are hidden after 7 days and deleted within the hour after that.
A merchant's payments and records are kept for the life of the account. Closing the account removes your sign-in, every device's session, your credentials and the bank account at once. Closing here closes only your payments account. Your iamlukia.com identity stays. If you erase that identity at iamlukia.com, this account is closed too; its payments, records and audit trail are then kept for five years, read-only, and deleted after that.
- Alert history: 30 days.
- Sign-in: a session lasts 30 days; spent sign-in hand-offs, used links and ended sessions are deleted by the same hourly job.
Cookies
- demo_visitor
- The random visitor id. 7 days.
- demo_merchant
- Your signed-in session; only its hash is stored. 30 days.
- demo_id_state
- Ties your return from iamlukia.com to the sign-in you started. Ten minutes.
- demo_app_return
- Sends you back to the app after a checkout the app started. One hour.
- JSESSIONID
- Protects this site's forms against forgery. Ends with the browser session.
Who else handles it
Fly.io
- Receives
- Everything this page lists as stored
- Why
- Hosting and the database, in Johannesburg.
Cloudflare
- Receives
- Every request to this site
- Why
- DNS and the edge every request passes through.
iamlukia.com sign-in
- Receives
- That you are signing in to this demo, and a check every 15 minutes that you still may
- Why
- It is the only way in. It is run by the same owner and tells this demo your email address and an opaque identifier.
Resend
- Receives
- Your email address and the message
- Why
- Sends this site’s emails: your payments link, team invitations, receipts and reminders.
PayFast
- Receives
- Each test payment, and anything you type on its page
- Why
- Its sandbox takes the payment, under its own terms.
Yoco
- Receives
- Each test payment, and anything you type on its page
- Why
- Its sandbox takes the payment, under its own terms.
Statuspage (PayFast)
- Receives
- Nothing about you
- Why
- Its public status page is read every five minutes.
Statuspage (Yoco)
- Receives
- Nothing about you
- Why
- Its public status page is read every five minutes.
Google Pay
- Receives
- Only if you choose it on the simulated card page
- Why
- That page then loads Google’s script in test mode.
A copy of each notification about a real-mode merchant's own payment is also sent to the site owner's webhook inspector (hooks.paidyup.com), and kept there only if that merchant connected this sandbox in it, in their own session.
The database is in South Africa. Cloudflare's edge and Resend may handle a request or an email outside it.