Is It Out of Scope? — Web development
Is adding a payment gateway integration out of scope for a web development project?
Yes, if it wasn't part of the original deliverables. It's native dev work, but payment integration carries real complexity and liability, so it needs its own scope.
This is core dev territory, but payment integration is a meaningfully bigger undertaking than most feature adds — PCI compliance considerations, error handling, webhook reliability, and testing across edge cases like failed or partial payments.
Is it out of scope?
Yes, if it wasn't part of the original deliverables. It carries enough complexity and liability that it warrants its own scoped quote rather than being folded into unrelated build work.
Clause typically implicated
Clause typically implicated
Deliverables clause→ — The original quote listed specific deliverables; payment gateway integration not named in that list is new, unscoped work with its own complexity.
Example contract wording
Example contract wording (illustrative, not legal advice)
A payment gateway integration wasn't part of the original deliverables — between compliance considerations and edge-case handling, it's substantial enough to warrant its own scoped quote. I'll put one together.
How MarginFlow flags it
MarginFlow flags payment-integration requests outside_scope when not named in the contract's deliverables list, and notes the added complexity relative to typical feature-add requests in its explanation.