Shared payments, explained.
Zeronda starts with evidence. Here is exactly what the beneficiary, sponsor and payment provider each do.
Register an invoice
See what Zeronda stores, extracts and checks before anyone is asked to pay.
Open tutorial 3 min readReview as a sponsor
Understand the evidence, validation caveat and hard invoice-total cap.
Open tutorial 2 min readKnow the privacy boundary
Learn which records are shared and which payment details remain inside Stripe.
Open tutorialThe amount comes from the invoice.
The beneficiary uploads the original file and names the intended sponsor. They do not type the amount they hope to receive.
- 1Store and identify
The private file is signature-checked, hashed and entered into the invoice registry.
- 2Extract and compare
Zeronda reads supplier, number, dates, currency and totals, then checks for exact and semantic duplicates.
- 3Invite only after checks
Failed evidence is blocked. Passed evidence gets a private sponsor link.
A careful yes, invoice by invoice.
The sponsor reviews the original evidence and chooses any positive amount up to the remaining total. Zeronda cannot create Checkout for more.
Shared evidence. Private payment credentials.
The boundary is simple and predictable.
Payment details stay inside Stripe Checkout.
Nothing hidden in the small print.
Does a passed check prove the invoice is genuine?+
No. It confirms the document passed the automated checks Zeronda ran. Sponsors still make their own decision.
Can the same invoice be submitted twice?+
Zeronda blocks exact-file and semantic duplicates for the beneficiary and logs every attempt. Corrected invoices need an explicit supersession path.
What if I was invited before signing up?+
Use the same work email. Requests attached to that normalized email appear in your sponsor inbox.
Does Zeronda store payment credentials?+
No. Stripe Checkout receives the sponsor’s test payment details. Zeronda stores safe provider references and outcomes.