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.

01

How you pay

Invoice and bank transfer available now

  • Invoice in English, priced in USD, with the transfer details on it
  • Paid by international bank transfer, the way most companies already pay contractors abroad
  • Your bank’s outgoing transfer fee is yours, which is the normal arrangement
  • Receipt sent by email as soon as the money lands

Card payments not yet

  • I do not take card payments today, and I would rather say so than let you find out at checkout
  • If that changes, this page says so before anything else does
  • If paying by card is the only way your company can pay, tell me early and I will look into it before we agree the scope
02

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.

Under $2,500Paid in full up frontSmall enough that splitting it costs us both more in admin than it protects
$2,500 and up40% to start, 60% on handoverThe second invoice goes out after you have the working system and have checked it
Large buildsSplit by phaseEach phase has its own number and its own delivery date. You can stop after any phase
03

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.

  1. Source code in your own account from day one

    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.

  2. Deployed and running

    Set up on your hosting and your domain, configured, and tested with you before anything is switched on for real users.

  3. 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.

  4. 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.

04

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
  • 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 madarotsa@gmail.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.

05

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
06

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.