Skip to content

Legal & policies

Payment Policy

Project-specific quotations, payment verification, disputes, and the relationship between payment and handover. Effective 29 October 2026.

Effective 29 October 2026Applies as written; a signed engagement agreement prevails where it differs.

Payment Policy

Project-specific quotations, payment verification, disputes, and the relationship between payment and handover. Effective 29 October 2026.

1. Purpose

This Policy describes general payment handling for TECH360 services. The quotation, invoice, approved SOW, and project agreement control the amount, currency, method, timing, and milestones for an engagement.

2. Quotations and Scope Approval

The quote should be read with the SOW, which identifies included work and applicable commercial terms. A project-specific written agreement and approved Scope of Work (SOW) define the deliverables, price, schedule, revision allowance, payment milestones, support, and ownership or licence terms. A website description, proposal draft, or preliminary discussion does not replace that approval.

3. Payment Schedule

The payment schedule is project-specific and appears in the approved quotation, invoice, and SOW. An engagement may use one payment, stages, or milestones; no universal advance amount, percentage, or milestone schedule applies. Changes to agreed fees or payment timing must be documented and approved.

4. Accepted Payment Methods

Available payment methods are those expressly listed on the applicable invoice or otherwise confirmed by TECH360 in writing. Availability may vary by Client, location, currency, and provider. This Policy does not represent that a particular gateway, merchant account, bank account, or payment method is approved or available.

5. Payment Verification

Payment is treated as received only after TECH360 can reasonably verify that funds have cleared, using available transaction records and confirmation from the relevant provider or financial institution. A screenshot, payment instruction, or pending transfer alone is not conclusive proof of cleared funds.

6. Payments Made Using Another Person's Card

Clients must use a payment method they are authorized to use. If a payment is made using another person's card or payment account, TECH360 may reasonably request evidence that the legitimate account holder authorized the transaction. An email address or statement from the Client alone does not conclusively establish cardholder identity or consent. If a material authorization concern remains unresolved, TECH360 may pause commencement, further work, or handover while it investigates, consistent with the agreement, applicable law, and payment-provider rules. A third-party payment is not automatically fraudulent.

7. Email and Transaction Verification

Billing or refund requests should preferably come from the email address associated with the original order or payment. TECH360 may request reasonable additional verification if details differ, using relevant records such as the order email, Client/project ID, invoice number, transaction reference, payment date and amount, approvals, correspondence, and delivery or handover evidence. Where relevant and lawfully available, TECH360 may consider IP address and timestamp records. Email or IP matches and mismatches are evidence only, not conclusive proof of identity, authorization, or fraud; IP addresses can change due to mobile networks, VPNs, and shared connections. Do not send passwords, card security codes, or complete payment-card details.

8. Currency, Taxes, and Fees

Currency, any applicable taxes, bank charges, foreign-exchange costs, and payment-provider fees are stated in the applicable quotation or invoice where known and relevant. Responsibility is determined by that document, provider rules, and applicable law; no tax or fee treatment is promised universally.

9. Failed, Pending, Reversed, or Disputed Payments

A failed, pending, reversed, or disputed transaction may not satisfy an invoice unless and until the applicable amount is verified as cleared. TECH360 may contact the Client or provider to reconcile the record. Any pause, collection step, or delivery hold must be consistent with the agreement, provider rules, and applicable law. TECH360 cannot unilaterally cancel or decide a provider dispute.

10. Refunds

Refund decisions follow the Refund Policy and are assessed against the approved SOW, project agreement, work completed, delivery, payment records, any defect or non-delivery allegation, applicable law, and provider rules. Properly completed and conforming work is generally not refundable merely because the Client changes their mind, subject to legal and contractual rights.

11. Final Payment and Source-Code Handover

Unless otherwise agreed in writing, final source-code handover takes place after all required project payments have been received and cleared. Any suspension or withholding of work or delivery must follow the approved agreement and applicable law.

12. Invoices and Records

TECH360 may maintain quotations, approved SOW versions, invoices, transaction references, payment confirmations, relevant communications, and handover evidence for project administration, accounting, security, and dispute resolution, subject to applicable retention requirements. Records should not include unnecessary payment credentials.

13. Contact Information

Contact TECH360 LLC at info@bdtech360.com. Please include the relevant project or invoice reference, but do not email passwords, full payment-card details, or card security codes.

Questions about this policy?

Write to info@bdtech360.com or start a live chat with our team (on any page) quoting your Client ID. Policy questions are answered by the team that wrote the policy.