Payment and handover
This page covers how you pay, when you pay, and what you actually receive. You get the full number once, in writing, before anything starts, including the third-party costs that do not come to me.
How you pay
Card pay now
- Visa and Mastercard on the payment page, and Link if you already use it
- Fixed-price packages are bought straight from the package page, and the work starts as soon as the payment clears
- Stripe hosts the card form, so your card number never reaches this website
- Receipt emailed automatically the moment the payment goes through
Invoice and bank transfer on request
- Invoice in English, priced in USD, with the transfer details on it
- For finance departments that need an invoice to pay against, and for quoted work
- Your bank’s outgoing transfer fee is yours, which is the normal arrangement
- Receipt sent by email as soon as the money lands
When you pay, and in how many parts
One rule runs through all of it: you never pay ahead for work that does not exist yet. Every stage after the first is invoiced only after you have seen and accepted the work before it.
What you receive
Everything I build is software, so there is nothing to ship physically. Handover happens electronically, inside the window written on your scope document.
Source code in your own account
On a project paid in full up front, the repository lives in your GitHub account from the first day of work, not at the end. You are holding the work the entire time and can hand it to somebody else whenever you want. On a project split into two instalments, you use the real system on my server throughout the build and the repository transfers to your account once the final instalment clears.
Deployed and running
Set up on your hosting and your domain, configured, and tested with you before anything is switched on for real users.
Documentation written in English
A user guide with screenshots, a README your own developer can follow, and English comments in the code. Sent as PDF within one business day of handover.
60 days of support from the day you accept
Longer than the Thai side gets, because the handover pack and the contract are part of what you are paying for. Full terms on the support and refunds page.
Cancelling, refunds and disputes
Before work starts full refund
- Cancel any time before I begin and you get everything back, no reason needed
- Email is enough. There is no notice period and no cancellation fee
After work starts no refund
- Once I have started, the time is spent and cannot be recovered
- You keep everything produced up to that point, including the source code
- Cancelling covers work not yet handed over. Once everything agreed is delivered and accepted, the final instalment is payment for work you already have. If it is not what we agreed, tell me and I fix it before invoicing
- On phased projects you can stop after any phase and owe nothing for phases not started
If something is wrong with the work, talk to me before your bank. Email phisit@zyntronlabs.com and I answer within one business day. Anything that is my mistake, I fix at no charge during the support period. A card dispute or a reversed transfer takes weeks and neither of us gets a working system out of it. Full terms are on the support and refunds page.
Costs that are not mine
These are listed on your scope document, so none of them appear later as a surprise
- Domain registration, roughly $15–25 a year, always registered in your name and not mine
- Hosting or servers, depending on the size of the system. Plenty of small projects genuinely run on free tiers and I will tell you when yours does
- AI usage, for projects that use it, roughly $10–60 a month based on real usage
- Google Play developer account, a one-time $25, for mobile app projects
Where I can and cannot work
I work with clients worldwide with one exception. I cannot supply software development, IT consulting or security testing to anyone located in Russia, Belarus, Cuba, Iran, North Korea, Syria, or the occupied regions of Ukraine. That is a legal restriction on this kind of service, not a preference, and it applies no matter who is paying.
One more thing about security work. I only test systems you can show me written permission for, and the permitted scope goes into the contract before I touch anything. No exceptions, including when the site is obviously yours. It protects both of us.