Table of Contents
(not the finale release, draft for review. contact us at legal@supportcall.com.au fir the finale and current version)
SupportCALL — Debit Order Terms & Authority
Document status: Master customer payment and debit-authority terms
Version: 1.0
Next review: No later than 12 months after the last review, or sooner following a material legal, banking, payment-provider or operational change
Document owner: SupportCALL
Applies to: Customers who authorise SupportCALL to collect amounts payable by direct debit, debit order or another recurring electronic payment arrangement
IMPORTANT — BEFORE PUBLICATION
This document is intended to govern the contractual relationship between SupportCALL and a Customer concerning an authorised debit or recurring electronic payment arrangement.
Do not publish this document as final until every item marked [ACTION REQUIRED] has been verified against the actual SupportCALL payment process, payment provider, financial institution requirements, debit scheme and Customer agreement.
In particular, SupportCALL must verify:
* the actual payment provider; * the actual debit scheme or payment mechanism; * whether the authority is created electronically, on paper or through a payment-provider-hosted mandate; * the required notice period for variable amounts; * the actual debit retry process; * applicable dishonour or failed-payment fees; * the exact cancellation process; * the provider's dispute and chargeback process; * the provider's privacy and data-handling arrangements; and * any mandatory wording prescribed by the relevant payment provider or financial institution.
Do not insert or invent provider-specific wording until the actual provider has been identified and its current requirements have been checked.
1. Purpose
These Debit Order Terms & Authority (“Debit Terms”) establish the terms under which a Customer may authorise SupportCALL to collect amounts properly payable under an applicable SupportCALL agreement using a direct-debit, debit-order or recurring electronic payment arrangement.
These Debit Terms are a payment mechanism and do not independently create a debt.
The underlying obligation to pay arises from the applicable:
* Service Application & Agreement; * quotation; * proposal; * statement of work; * service schedule; * invoice; * subscription; * purchase; * or other agreement between the Customer and SupportCALL.
2. Relationship with other SupportCALL documents
These Debit Terms must be read together with:
* SupportCALL Terms of Service; * SupportCALL Service Application & Agreement; * SupportCALL Privacy Policy; * the applicable quotation, proposal or statement of work; * the applicable invoice or billing statement; and * the terms of the applicable payment provider or debit scheme.
If there is an inconsistency between documents, the following order applies, to the extent legally applicable:
* mandatory applicable law; * mandatory payment-provider or debit-scheme requirements; * a signed agreement expressly varying these Debit Terms; * the applicable Service Application & Agreement; * the applicable quotation or service schedule; * these Debit Terms.
Nothing in these Debit Terms is intended to exclude, restrict or modify a right, guarantee, remedy or obligation that cannot lawfully be excluded, restricted or modified.
3. Contracting entity
The SupportCALL entity authorised to receive payment will be the entity identified in the applicable Service Application & Agreement, quotation, invoice or other contractual document.
The current SupportCALL Privacy Policy identifies:
* Australian entity or business: David H Maree Sole-Trader * ABN: 21 498 105 915 * Principal place of business: Launceston, Tasmania, Australia * South African entity: SupportCALL (Pty) Ltd * South African registration: 2013/102719/07
The applicable contracting entity must be confirmed before the debit authority is activated.
4. Definitions
For these Debit Terms:
“Customer” means the person or organisation responsible for the applicable SupportCALL account.
“Debit Authority” means the authority provided by the Customer permitting SupportCALL or its nominated payment provider to initiate an authorised payment.
“Debit Date” means the date on which a debit is scheduled to be processed.
“Payment Provider” means the financial institution, payment processor, direct-debit provider or other authorised service used to process the payment.
“Underlying Agreement” means the agreement under which the Customer owes the relevant amount to SupportCALL.
“Variable Amount” means an amount that may differ between billing periods because of usage, additional services, approved purchases, taxes, expenses, changes permitted by the Underlying Agreement or another legitimate billing variation.
5. Customer details
| Field | Customer information |
| ——————————- | ————————- |
| Legal name / entity | [CUSTOMER TO COMPLETE] |
| Trading name | [CUSTOMER TO COMPLETE] |
| ABN / ACN / registration number | [CUSTOMER TO COMPLETE] |
| Customer / account number | [SUPPORTCALL TO COMPLETE] |
| Billing contact | [CUSTOMER TO COMPLETE] |
| Billing email | [CUSTOMER TO COMPLETE] |
| Telephone | [CUSTOMER TO COMPLETE] |
| Service address | [CUSTOMER TO COMPLETE] |
| Billing address | [CUSTOMER TO COMPLETE] |
6. Authority to debit
By completing and accepting the applicable Debit Authority, the Customer authorises SupportCALL and/or its nominated Payment Provider to initiate debits from the nominated payment account for amounts properly payable under the Underlying Agreement.
The authority is limited to amounts properly payable under the Customer's SupportCALL account.
The authority does not permit SupportCALL to:
* debit unrelated amounts; * debit arbitrary amounts; * alter the underlying contractual obligations without an applicable contractual basis; or * use the authority for a purpose unrelated to the Customer's SupportCALL account.
7. What may be debited
Subject to the Underlying Agreement, the Debit Authority may be used for:
* recurring service fees; * subscription fees; * approved project charges; * approved additional services; * hardware charges; * software or licensing charges; * hosting charges; * approved third-party charges; * approved travel or onsite charges; * applicable taxes; * other properly invoiced charges; and * other amounts expressly authorised under the Underlying Agreement.
A debit does not make an otherwise disputed or invalid charge valid.
8. Fixed and recurring amounts
Where the Customer has agreed to a fixed recurring amount, SupportCALL may debit that amount according to the agreed billing frequency and payment schedule.
The agreed recurring amount must be recorded in the applicable Service Application & Agreement, quotation, subscription record or other contractual document.
9. Variable amounts
Where the Customer's charges may vary, SupportCALL may debit the amount properly payable for the applicable billing period, subject to:
* the Underlying Agreement; * any applicable quotation or service schedule; * applicable law; and * the rules of the Payment Provider or debit scheme.
The Customer will receive or have access to an applicable invoice, statement or other billing record identifying the amount payable.
[ACTION REQUIRED — INSERT THE ACTUAL CUSTOMER NOTICE PROCESS AND NOTICE PERIOD FOR VARIABLE DEBITS.]
10. Debit frequency
The agreed billing frequency is:
* [ ] Weekly * [ ] Fortnightly * [ ] Monthly * [ ] Quarterly * [ ] Six-monthly * [ ] Annually * [ ] Other: ______________________________
The actual processing date may be affected by weekends, public holidays, banking days, processing cut-offs or Payment Provider requirements.
11. Debit date
Preferred debit date:
Day: ______________________________
Where the selected date is not a processing day, the debit may be processed on the next applicable processing day, subject to the Payment Provider's rules.
The Customer remains responsible for ensuring that sufficient funds are available when the debit is scheduled.
12. Advance notice and billing information
SupportCALL will provide billing information in accordance with the Underlying Agreement and any applicable legal, banking or Payment Provider requirements.
The billing information may include:
* invoice number; * billing period; * services supplied; * additional charges; * taxes; * amount payable; * scheduled debit date; and * payment status.
[ACTION REQUIRED — VERIFY THE ACTUAL NOTICE METHOD USED BY SUPPORTCALL.]
13. Sufficient funds
The Customer is responsible for ensuring that sufficient cleared funds or available payment capacity are available for an authorised debit.
If a debit fails because sufficient funds are unavailable, the underlying amount remains payable unless otherwise agreed or required by law.
14. Failed or dishonoured debit
A debit may fail for reasons including:
* insufficient funds; * incorrect account details; * closed account; * account restrictions; * bank rejection; * Payment Provider rejection; * technical failure; * expired or cancelled authority; * fraud or security controls; or * another banking or processing reason.
Where a debit fails, SupportCALL may, subject to the applicable agreement and law:
* notify the Customer; * request another payment method; * issue an invoice; * retry the debit where permitted; * suspend affected services where permitted; or * take another lawful step available under the Underlying Agreement.
15. Debit retry
SupportCALL may retry a failed debit only where permitted by:
* the applicable Debit Authority; * the Payment Provider; * the relevant debit scheme; * applicable law; and * the Underlying Agreement.
[ACTION REQUIRED — INSERT ACTUAL RETRY POLICY, INCLUDING MAXIMUM NUMBER OF RETRIES AND TIMING.]
16. Dishonour and payment fees
Any dishonour, failed-payment, administration or other payment-related fee charged to the Customer must:
* be permitted by applicable law; * be permitted under the Underlying Agreement; * be properly disclosed; and * reflect the actual contractual or legally recoverable amount.
[ACTION REQUIRED — INSERT ACTUAL SUPPORTCALL FEE, IF ANY.]
Do not publish a fee in this document until the actual amount and legal basis have been verified.
17. Changes to payment details
The Customer must notify SupportCALL through the approved process if:
* the nominated account changes; * the account holder changes; * the account is closed; * the payment method changes; * the Debit Authority is cancelled; or * the Customer believes the payment authority has been compromised.
SupportCALL may require a new Debit Authority before processing further debits.
18. Security of payment information
Customers must not send banking passwords, online-banking credentials, authentication codes, card security codes or other authentication secrets to SupportCALL.
Where SupportCALL uses a third-party payment-provider-hosted payment form or secure mandate process, the Customer should enter payment information directly into that approved environment.
SupportCALL personnel must not request a Customer's online-banking password.
19. Banking information retained by SupportCALL
SupportCALL will seek to minimise the collection and retention of payment information.
Where payment processing is performed by a third-party Payment Provider, payment information may be collected and processed directly by that provider.
[ACTION REQUIRED — VERIFY EXACTLY WHAT BANKING INFORMATION SUPPORTCALL STORES LOCALLY.]
The SupportCALL Privacy Policy explains how personal information and payment-related information are handled.
20. Payment provider
Payment Provider: [ACTION REQUIRED]
Payment method / debit scheme: [ACTION REQUIRED]
Payment-provider terms: [ACTION REQUIRED — INSERT VERIFIED LINK]
Payment-provider privacy notice: [ACTION REQUIRED — INSERT VERIFIED LINK]
Provider support contact: [ACTION REQUIRED]
Processing country/countries: [ACTION REQUIRED — VERIFY]
21. Cancellation of Debit Authority
The Customer may request cancellation of the Debit Authority using the approved SupportCALL process.
The Customer may also have rights to cancel or dispute a debit through its financial institution or Payment Provider.
Cancellation of the Debit Authority does not automatically cancel:
* the Underlying Agreement; * a subscription; * a minimum contractual term; * a project; * an invoice; * a purchase; or * another amount properly payable.
After cancellation of the Debit Authority, the Customer must use another approved payment method for amounts that remain payable.
22. Cancellation through the financial institution
Where the Customer cancels the Debit Authority through its financial institution, the Customer should also notify SupportCALL.
This enables SupportCALL to:
* stop future debit instructions where applicable; * update the Customer's payment record; * prevent unnecessary failed-payment processing; and * arrange an alternative payment method.
23. Timing of cancellation
A cancellation request may require processing time.
[ACTION REQUIRED — INSERT ACTUAL SUPPORTCALL PROCESSING TIME.]
A cancellation request received after a debit has already entered the Payment Provider's processing cycle may not stop that particular transaction.
Where this occurs, the Customer should contact SupportCALL promptly.
24. Disputed debit
If the Customer believes a debit is incorrect, the Customer should contact SupportCALL promptly.
The Customer should provide:
* Customer/account number; * debit date; * amount; * invoice number, where applicable; * transaction reference, where available; and * explanation of the dispute.
SupportCALL will investigate the matter.
The Customer retains any rights available under applicable law and the rules of the relevant payment scheme.
25. Unauthorised debit
If the Customer believes a debit was unauthorised, fraudulent or otherwise incorrectly processed, the Customer should contact:
* SupportCALL; and * the Customer's financial institution or Payment Provider where appropriate.
SupportCALL will cooperate with reasonable investigations.
26. Chargebacks and reversals
Where a Customer initiates a chargeback, reversal or payment dispute through a financial institution or Payment Provider, SupportCALL may provide relevant contractual, invoice and transaction information necessary to investigate or respond to the dispute.
SupportCALL will not treat a legitimate statutory right to dispute a transaction as a contractual breach merely because the Customer exercises that right.
Where a payment is validly reversed but the underlying amount remains properly payable, SupportCALL may request payment through another approved method.
27. Incorrect amount debited
If SupportCALL identifies that an incorrect amount was debited, SupportCALL will investigate and, where appropriate:
* correct the account; * refund an amount improperly collected; * apply a credit; * adjust a future invoice; or * take another appropriate corrective action.
The corrective method will depend on the circumstances, the Payment Provider and applicable law.
28. Duplicate debit
If the same amount is accidentally debited more than once, SupportCALL will investigate and, where appropriate, correct the duplicate transaction by refund, credit or another appropriate method.
29. Privacy
The collection, use, storage and disclosure of personal information associated with the Debit Authority is governed by the SupportCALL Privacy Policy.
Payment information may also be handled by the Payment Provider under its own terms and privacy policy.
The Customer should review the Payment Provider's privacy documentation where payment information is entered directly into the provider's systems.
30. Overseas processing
Payment information may be processed or accessed outside Australia where the selected Payment Provider or financial institution operates internationally.
[ACTION REQUIRED — VERIFY ACTUAL COUNTRIES BEFORE PUBLICATION.]
SupportCALL will make the disclosures required by applicable privacy law.
31. Changes to the Debit Terms
SupportCALL may update these Debit Terms where reasonably necessary because of:
* changes in law; * changes in banking requirements; * Payment Provider changes; * debit-scheme changes; * security requirements; * operational changes; or * changes to the SupportCALL payment process.
Where a change materially affects an existing Customer's contractual rights or obligations, SupportCALL will provide any notice or obtain any agreement required by applicable law or the Underlying Agreement.
A change to these Debit Terms does not retrospectively authorise an otherwise unauthorised debit.
32. Termination of the Debit Authority
The Debit Authority terminates when:
* the Customer validly cancels it; * SupportCALL cancels it; * the underlying service account is permanently closed and no further authorised debits are required; * the Payment Provider terminates the authority; * the nominated account becomes unavailable; or * another event occurs that lawfully terminates the authority.
Termination of the Debit Authority does not automatically terminate the Underlying Agreement.
33. Termination of the underlying service
Termination of a SupportCALL service is governed by the applicable Service Application & Agreement and Terms of Service.
The Customer remains responsible for amounts properly payable up to the effective termination date and for any other amounts that lawfully survive termination.
34. Australian Consumer Law
Nothing in these Debit Terms excludes, restricts or modifies a right or remedy that cannot lawfully be excluded, restricted or modified under the Australian Consumer Law or another applicable law.
The Debit Authority is a payment mechanism only.
It does not remove or reduce statutory consumer guarantees, cancellation rights, refund rights or other mandatory rights.
35. No waiver
A failure by SupportCALL to immediately exercise a right under these Debit Terms does not constitute a waiver of that right.
36. Severability
If a provision of these Debit Terms is found to be invalid, unlawful or unenforceable, that provision will be read down or severed to the minimum extent necessary.
The remaining provisions continue to operate to the extent permitted by law.
37. Records and audit trail
SupportCALL may retain records reasonably necessary to demonstrate:
* the existence of the Debit Authority; * the Customer's identity; * the date the authority was provided; * changes to the authority; * cancellation of the authority; * debit instructions; * invoices; * payments; * failed payments; * refunds; * disputes; and * relevant communications.
Records will be retained in accordance with applicable legal, accounting, tax, contractual and operational retention requirements.
38. Customer declaration
By accepting the applicable Debit Authority, I / we confirm that:
* I / we have read these Debit Terms; * I / we understand that the Debit Authority permits authorised payments to be collected; * I / we have authority to operate or authorise payments from the nominated account; * the information supplied is accurate; * I / we understand that the Debit Authority does not itself create the underlying debt; * I / we understand that cancellation of the Debit Authority does not automatically cancel the underlying service agreement; * I / we understand that failed payments may require another payment method; * I / we understand that disputed or unauthorised transactions may be raised with SupportCALL and, where appropriate, the financial institution or Payment Provider; and * I / we agree to the applicable SupportCALL service agreement and these Debit Terms.
39. Debit Authority record
| Field | Details |
| ————————— | ——————————– |
| Customer legal name | [CUSTOMER TO COMPLETE] |
| Trading name | [CUSTOMER TO COMPLETE] |
| Customer/account number | [SUPPORTCALL TO COMPLETE] |
| Debit frequency | [COMPLETE] |
| Preferred debit date | [COMPLETE] |
| Fixed amount | $[COMPLETE] |
| Variable amount permitted | [YES / NO] |
| Notice method | [COMPLETE] |
| Payment Provider | [COMPLETE] |
| Debit scheme | [COMPLETE] |
| Authority commencement date | [DATE] |
| Authority reference | [REFERENCE] |
| Authority status | [ACTIVE / CANCELLED / SUSPENDED] |
40. Nominated payment account
IMPORTANT:
Complete payment-account information only through the approved secure payment-authorisation process.
Do not publish completed banking information on this wiki.
Do not send banking passwords, authentication codes or online-banking credentials to SupportCALL.
| Field | Customer information |
| ————————- | ———————- |
| Account holder | [CUSTOMER TO COMPLETE] |
| Financial institution | [CUSTOMER TO COMPLETE] |
| BSB / routing information | [CUSTOMER TO COMPLETE] |
| Account number | [CUSTOMER TO COMPLETE] |
| Account type | [CUSTOMER TO COMPLETE] |
41. Authorised account holder
Full legal name: ___________________________________________
Position / authority: ______________________________________
Email: ___________________________________________________
Telephone: _______________________________________________
Signature: ________________________________________________
Date: ____________________________________________________
42. Electronic acceptance
Where this Debit Authority is accepted electronically, SupportCALL must retain an appropriate audit record showing, where applicable:
* Customer identity; * date and time of acceptance; * version of these Debit Terms; * version of the Debit Authority; * relevant Customer/account reference; * acceptance method; * IP address or other technical audit information where lawfully collected and reasonably necessary; * Payment Provider reference; and * cancellation or amendment history.
[ACTION REQUIRED — VERIFY THE ACTUAL ELECTRONIC ACCEPTANCE AND AUDIT DATA RETAINED BY SUPPORTCALL.]
43. SupportCALL processing record
| Field | SupportCALL record |
| ———————– | ————————————– |
| Customer/account number | [COMPLETE] |
| Authority received | [DATE / TIME] |
| Authority method | [PAPER / ELECTRONIC / PROVIDER-HOSTED] |
| Payment Provider | [COMPLETE] |
| Authority reference | [COMPLETE] |
| Verification completed | [YES / NO] |
| Verification date | [DATE] |
| Commencement date | [DATE] |
| First scheduled debit | [DATE] |
| Status | [ACTIVE / CANCELLED / SUSPENDED] |
| Cancellation received | [DATE] |
| Cancellation processed | [DATE] |
| Processed by | [NAME / SYSTEM] |
44. SupportCALL internal controls
SupportCALL should maintain internal controls so that:
* a Customer cannot be debited without an applicable authority; * the debit amount can be reconciled to an underlying invoice or authorised charge; * cancelled authorities are not unnecessarily used; * failed payments are recorded; * refunds and credits are traceable; * payment-provider references can be reconciled; * access to payment information is restricted; * sensitive payment credentials are never requested; * changes to payment details are appropriately verified; and * payment records can be produced for legitimate dispute, accounting, legal or audit purposes.
45. Security and fraud prevention
SupportCALL may apply reasonable verification controls before:
* changing payment details; * changing the nominated account; * changing the authorised account holder; * processing a refund; * cancelling a Debit Authority; * accepting an unusual payment instruction; or * responding to a suspected payment-fraud event.
These controls may require the Customer to use a previously verified contact method or the Payment Provider's secure process.
SupportCALL will not rely solely on an email requesting a change to banking details where additional verification is reasonably necessary.
46. Related SupportCALL documents
47. Contact
SupportCALL
Website: www.supportcall.com.au](https://www.supportcall.com.au|www.supportcall.com.au)
General enquiries: [support@supportcall.com.au](mailto:support@supportcall.com.au)
Privacy enquiries: [privacy@supportcall.com.au](mailto:privacy@supportcall.com.au)
[ACTION REQUIRED — VERIFY ALL PUBLISHED CONTACT DETAILS BEFORE PUBLICATION.]
48. Document control
| Field | Details | |
| ———————- | —————————————– | ——————————— |
| Document | SupportCALL Debit Order Terms & Authority | |
| Version | 1.0 | |
| Effective date | [ACTION REQUIRED] | |
| Last reviewed | [ACTION REQUIRED] | |
| Next review | [ACTION REQUIRED] | |
| Owner | SupportCALL | |
| Related Privacy Policy | Privacy Policy | |
| Related Terms | Terms of Service | |
| Related Application | Service Application & Agreement | |
| Status | [DRAFT / APPROVED / PUBLISHED] |
Appendix A — Publication verification checklist
Before publishing this document, SupportCALL must verify:
* [ ] Contracting entity * [ ] ABN / registration details * [ ] Payment Provider * [ ] Debit scheme * [ ] Provider terms * [ ] Provider privacy policy * [ ] Provider processing countries * [ ] Variable-debit notice requirements * [ ] Debit frequency * [ ] Debit date * [ ] Failed-payment process * [ ] Retry process * [ ] Dishonour fees * [ ] Cancellation process * [ ] Cancellation processing time * [ ] Dispute process * [ ] Chargeback process * [ ] Refund process * [ ] Payment-information retention * [ ] Electronic-authority audit trail * [ ] Banking-detail change verification * [ ] Customer notification process * [ ] Privacy disclosures * [ ] Website contact details * [ ] Legal review * [ ] Final version number * [ ] Effective date
Appendix B — Change history
| Version | Date | Change | Author / owner |
| ——- | —— | ——————————————– | ————– |
| 1.0 | [DATE] | Initial master Debit Order Terms & Authority | SupportCALL |
