This page tells you exactly when you get your money back, when you don’t, and how to ask. Read it before you order. Ten minutes here saves an argument later.
Payment runs in two parts. You pay [50%] to start and the other [50%] after you’ve reviewed the work and you’re happy with it. There’s no full prepayment and no rush surcharge.
1. The quick version
| Situation | What you get | When to tell us |
|---|---|---|
| Cancelled before we assign a developer | Full refund | Within 2 hours of payment |
| Cancelled after work has started | 0% to 70% | Reviewed case by case |
| Rush order, deadline under 24 hours | Full refund | First hour only |
| We delivered late | Full refund | No conditions attached |
| Work misses the brief and can’t be fixed | Full refund | Within the 14 day window |
| Charged twice | Full refund of the duplicate | Within 3 working days |
| Charged too much | Full refund of the surplus | Within 3 working days |
| You’ve already submitted or shared the work | No refund | Order closes at that point |
Details below.
2. Cancelling in the first 2 hours
Cancel within 2 hours of payment and you get everything back. You don’t need to give a reason and we won’t ask for one.
The clock starts at the timestamp on your payment confirmation, not when you uploaded the brief and not when we sent the quote. Email, the contact form, and WhatsApp all count as valid notice. Nobody has started work yet, so the order closes cleanly.
3. Cancelling after work has started
Once your brief goes to a developer, a cancellation gets somewhere between nothing and 70% back, depending on where the work stands.
Three things set the number:
- How much of the solution is already written.
- How close the deadline is.
- Whether you’ve already received partial code, a draft, or progress notes.
Cancelling two hours into a five day job gets you a lot more than cancelling on day four. That’s the whole logic behind it.
Near the deadline. In the last quarter of the project timeline there’s no refund. By that point the work is finished or nearly finished, and it has value to you whether you formally cancel or not.
Rush orders. If your deadline is under 24 hours, the full refund window is the first hour, not two. Rush work starts the moment payment clears, and on a six hour deadline a real chunk of the solution exists by the 90 minute mark. After that first hour, partial refunds apply on the same three factors above.
4. We delivered late
If we miss the agreed deadline, you get 100% back. No conditions, no negotiation, no processing fee shaved off the top.
The deadline sits on your order confirmation. Our developers work to a buffer of a few hours ahead of it. If that buffer ever looks like it’s going to fail, we contact you before the deadline rather than after it, and you pick: extend it, or take the full refund. Your choice, not ours.
5. The work missed the brief
If the delivered work doesn’t do what the brief and rubric asked for, we fix it free inside the revision window (section 9). If it still doesn’t comply after that, you get a full refund.
To move fast on this, send us four things: the original brief, the rubric, the delivered work, and a list of the specific points where they don’t match.
Specific complaints get resolved in a day. Here’s what specific looks like:
- The rubric asked for a recursive solution and the code iterates.
- The brief said unit tests on three functions and only one is covered.
- The course runs a particular language version and the code uses syntax that version rejects.
- The brief required third normal form and the schema isn’t normalized.
- The rubric said the code has to pass the course linter and it doesn’t.
“The code is bad” or “this isn’t what I expected” doesn’t give us anything to work with. Point at the line in the rubric and we’ll deal with it.
6. Originality and similarity scores
Everything we deliver is written from scratch for your brief. No AI generation, no recycled solutions from another student’s order.
For written deliverables like reports and documentation, a confirmed plagiarism finding gets you a full refund. Send us the report from Turnitin, SafeAssign, or a comparable tool within 24 hours of delivery. We verify it and refund within one business day.
Source code is a different story, and you should know why before you order.
Code similarity tools like MOSS, JPlag, Codequiry, and the checkers built into Gradescope will flag original code as similar to public code. They can’t really avoid it. Standard imports match. Loop structures match. A function called main() matches. Variables named i, j, and x match. Two students who both solve the same textbook problem correctly will produce code that looks alike, because there are only so many correct ways to write a binary search.
Scores in the low double digits on source code are routine on legitimate original work. A score on its own isn’t evidence of copying. Bring us a report showing a high match on the substantive logic rather than on boilerplate, and we’ll investigate it properly and refund if we find a problem.
7. Charged twice or charged too much
Duplicate order. It happens. Payment confirmation lags, you hit submit again, or a browser tab reloads mid-checkout. Tell us within 3 working days and we refund the duplicate in full. The original order carries on as planned. No questions, no paperwork beyond the two order IDs.
Overpayment. Same deal for a surplus, whether it’s a double charge on the processor’s side or a payment for more than the quoted figure. Full refund of the excess.
We send the refund instruction the day we approve it. How fast it lands depends on your bank, usually 3 to 7 business days.
8. What counts as accepting the work
Once you accept and use the work, the order is final and refunds close.
These count as accepting and using it:
- Uploading it to a course portal like Canvas, Blackboard, Moodle, Gradescope, or anything similar.
- Sending it to an instructor, a TA, or a grader.
- Sharing it with a study group, a forum, another tutor, or anyone outside the order.
- Merging it into a file you submit for credit under your name.
These do not count:
- Opening it.
- Downloading it to your machine.
- Running it locally.
- Reading it and asking us questions about it.
So review it properly first. Run the code, read the comments, check it against the rubric line by line. Anything you raise before you submit or share goes down the normal refund path. Anything you raise after doesn’t.
One piece of advice we’ll give you even though it costs us money: don’t submit work you haven’t read and can’t explain. If something in it doesn’t make sense to you, ask us before the deadline, not after the grade comes back.
9. Free revisions
Revisions are free for [7] days from delivery. Your developer fixes anything where the work doesn’t match the brief and the rubric you supplied at order time. No charge, no argument.
Covered: missing requirements, rubric mismatches, bugs, and code that won’t run in your course’s environment.
Not covered: new features, expanded scope, requirements that appeared after you ordered, or a change of direction. Those get a fresh quote.
After [7] days, revisions become chargeable.
If a fix inside the window still doesn’t bring the work into line with the rubric, and the issue can’t be resolved, you get a full refund within 5 business days.
10. The 14 day claim window
Refund claims that arrive more than 14 days after delivery aren’t eligible. That covers every category on this page.
Inside 14 days, every claim gets read and assessed individually. Outside it, the order is closed for refund purposes.
11. When refunds don’t apply
- You’ve submitted, shared, or used the work for credit.
- The claim arrives after the 14 day window.
- You have no specific evidence, just a general complaint.
- You changed the requirements mid-project and the developer declined the added scope.
- You stopped answering messages during the project, so the developer couldn’t get the clarification they needed.
- The deadline has passed and the completed work was delivered on time.
Every decision gets written down and the reasoning goes to you in plain language. You won’t get a one line “denied” from us.
12. Talk to us before you file a chargeback
If something’s wrong, email us. We answer within one business day and most problems get fixed the same day.
Filing a chargeback with your bank before you’ve contacted us ends your refund eligibility under this policy. Not because we’re being petty about it, but because a chargeback takes the decision out of our hands and gives it to a bank that has never seen your rubric. Give us 14 days from when you first raise the issue. If we haven’t sorted it by then, take it to your bank with our blessing.
13. How to ask for a refund
- Email [support@domyprogramminghomework.us] or use the contact form. Include your order ID, the delivery date, what went wrong, and your evidence: the rubric, the mismatch list, a grade screenshot, or a similarity report.
- We confirm receipt within 1 business day and pass it to a project manager.
- You get a written decision within 3 business days, with the reasoning behind it.
Disagree with the decision? Ask for a second look. A different project manager reviews the file from scratch and comes back within 5 business days. That one is final.
14. Timing
Approved refunds enter processing within 7 business days of approval. After that it’s down to your bank, usually another 3 to 10 business days depending on the country and the payment method.
We refund the original amount in the original currency. Bank fees, currency conversion charges, and intermediary deductions sit outside our control and aren’t ours to cover.
15. Discretion
We keep the right to make a judgment call on unusual cases: odd project scope, a platform outage, a mid-project change nobody could have seen coming.
Discretion only ever works in your favor. We won’t use it to give you less than this policy says you’re owed.
16. Changes to this policy
We can update this policy. Changes take effect from the date posted here. Your order runs under whichever version was live when you paid, not whichever version is live when you complain.
17. Contact
- Refunds: [support@domyprogramminghomework.us]
- General: [hi@domyprogramminghomework.us]
- WhatsApp: the chat button on the site
Reply times run 4 to 12 hours on weekdays and up to 24 hours over the weekend.
Disclaimer. What we deliver (code, database work, technical reports, written explanations, and tutoring sessions) exists as reference and study material. How you use it is your decision and your responsibility. This policy covers the commercial transaction between you and us. It doesn’t promise any academic result.