Payment trust centre · No public arbitrary checkout
See the agreement before money moves.
A polished checkout is not protection by itself. Confidence comes from a traceable scope, a controlled milestone, secure provider processing, fair cancellation rules and evidence of what was accepted and delivered.
Version · 30 August 2026
No surprise invoice.
The payment request is issued only after the proposal and statement of work are accepted.
No card data stored here.
Card, bank, PIN and OTP details stay inside the approved provider-hosted checkout.
Every gate leaves evidence.
Reviews, approvals, change requests, launch checks and handover are kept in the project decision trail.
Before you pay
Four checks built into the request.
The studio does not publish a buy-now button for custom work. A real client receives a private reference after scope and commercial terms are agreed.
A named scope
You receive a written statement of work with deliverables, exclusions, dependencies, timing, revision gates and one billing currency.
An agreement reference
The payment request names the accepted scope version and agreement reference. If they do not match your copy, do not pay.
A milestone—not a vague deposit
Every amount is tied to a specific reservation, approval point, build stage, launch or handover outcome.
A review page on this domain
Your private link shows the amount, currency, milestone, delivery window, policy version and payment status before checkout opens.
Secure payment boundary
Provider-hosted checkout. Server-verified result.
The private review page starts on this website. When you choose to pay, checkout is handled by Razorpay. This studio does not ask you to send card credentials, bank login details, a PIN or an OTP by email, WhatsApp or a project form.
A return to the website is never treated as proof of payment. The milestone changes to paid only after the provider sends a cryptographically signed server notification that matches the issued reference.
Available methods and currencies can vary by the client's country, provider approval and risk checks. The checkout shows what is actually available before money moves.
Read Razorpay's security information ↗Proof trail
What you can keep.
Refund and correction path
No blanket “no refunds” trap.
Eligibility follows the signed scope, work actually performed, accepted milestones, service deficiencies and mandatory legal rights. The published policy explains timing and escalation.
Read refund rules →Digital fulfilment
A handover, not a disappearing act.
The agreed delivery includes review links, launch checks and transfer of the final accounts, files or documentation named in the statement of work.
Read delivery rules →Important honesty boundary
Trust is a process, not a badge collection.
This site does not claim escrow, legal-firm review, government registration, payment-provider approval, guaranteed revenue or guaranteed search ranking unless that exact fact is documented for the engagement.
For high-value or regulated work, either side may request identity checks, a lawyer-reviewed agreement, tax documentation or a mutually agreed escrow/platform route before signing.
The person accountable
A real name behind the scope and handover.
I'm Sohan Vyaparee. I personally direct the strategy, visual system, build decisions and launch quality. AI helps me move research and implementation faster; it does not replace the named human responsible for your project.
Before payment, the contracting identity on your SOW and invoice must match the identity in the private payment record. If it does not, stop and verify through the existing project conversation.