QuickPay Terms of Use

2.1These QuickPay Terms of Use govern the use of QuickPay by every User, including Residents, unit owners, tenants, occupiers and other payers, and by Collecting Entities.

2.2The Qornerstone Platform Terms of Use at qornerstone.com/terms-of-use apply to QuickPay as part of the Platform. Where they conflict with these QuickPay Terms in relation to a QuickPay transaction, these QuickPay Terms prevail.

2.3Where a Collecting Entity has entered into a QuickPay Services Agreement with the Provider, that agreement prevails over these QuickPay Terms as between the Provider and that Collecting Entity. These QuickPay Terms continue to govern the relationship between the Provider and each User.

2.4The Provider. QuickPay is supplied by one of two companies, depending on the Collecting Entity's licence. In these Terms "we", "us" and "our" mean that entity.

2.5How QuickPay is operated. IBASE holds the contract with the Payment Partner under which the PayNow rights of operation for QuickPay are conferred on IBASE. IBASE confers those rights on Qornerstone Pte Ltd for the purpose of operating QuickPay for Subscription Licence customers. The Collection Account is held in IBASE's name for both channels and operates only as a vehicle for the solution, as described in clause 4.4.

"Collecting Entity"

The management corporation, building owner or other party for whose account a payment is collected through QuickPay, and includes a managing agent or integrated facilities management company acting on behalf of that party.

"Commercial Entity"

A Collecting Entity that is not a Non-Profit Entity.

"Collection Account"

An account maintained and operated by the Payment Partner in the name of IBASE, through which Transaction funds may pass before settlement to a Beneficiary Account.

"Beneficiary Account"

The bank account, held in the name of the Collecting Entity or the property it collects for, into which settlement is made.

"Non-Profit Entity"

A management corporation constituted under the Building Maintenance and Strata Management Act 2004, a subsidiary management corporation, a charity registered under the Charities Act 1994, a society registered under the Societies Act 1966, a company limited by guarantee that does not distribute profits to its members, or another entity that we accept in writing as operating on a not-for-profit basis.

"Payment Partner"

A bank, payment institution or payment service provider engaged in processing or settling Transactions, appointed by us from time to time.

"Platform Fee"

The fee for a Transaction set out in section 5.

"Transaction"

A QuickPay payment as described in clause 7.1.

"User"

Any person who initiates or attempts a payment through QuickPay.

4.1How it works. A QuickPay payment follows these steps:

1. an invoice, statement, booking charge or deposit is generated in the Platform;
2. we transmit the invoice details to the Payment Partner, which creates a PayNow QR code carrying the amount, a unique transaction reference and the Collection Account as the beneficiary;
3. the User pays using that QR code. The funds move by PayNow through the national payment infrastructure to the Collection Account;
4. the Payment Partner sends us an inward credit notification, which we record in an incoming payments ledger on the QuickPay server;
5. on the basis of that notification we reconcile the payment to the invoice, create the receipt and post to the accounting ledgers;
6. the QuickPay server generates an automated sweeping instruction to the Payment Partner to transfer the payment amount, less any applicable Platform Fee, to the Beneficiary Account at 11.00am on the next day; and
7. the Payment Partner makes that transfer, and we record it in an outgoing payments ledger and tally the two ledgers daily so that every inward credit, less any Platform Fee, is matched to an outgoing payment from the Collection Account.

4.2Our role. Our role in QuickPay is the processing of data and the automated instruction of transfers. We prepare and transmit invoice data, receive and record payment notifications, reconcile and receipt payments, and generate the automated sweeping instructions described in clause 4.1(f). We do not collect, receive, hold or apply funds for our own account, and we cannot operate the Collection Account other than by automated server-to-server instruction. The collection, clearing, movement and settlement of funds are performed by the Payment Partner and the national payment infrastructure. In relation to Personal Data contained in the data we process, we act as the Collecting Entity's data intermediary, as set out in section 10.

4.3The Payment Partner's role. The Payment Partner is the licensed payment processor. It is responsible for encoding the payment instruction, for the collection, clearing and settlement of funds, and for the operation of the accounts through which those funds pass. The Payment Partner is licensed under the Payment Services Act 2019, and QuickPay operates within that partner's licensing and collection framework. We will disclose the identity of the Payment Partner to any Collecting Entity or User on request.

4.4QuickPay covers PayNow payments only. The movement of funds between the payer's bank and the Collection Account is effected through the PayNow service and the national payment infrastructure. Clearing and settlement are performed by the Payment Partner and the banking system.

4.5We are not a bank, a deposit-taking institution, a payment service provider or a party to the underlying payment obligation between a User and a Collecting Entity. We do not guarantee, insure or assume that obligation. A User's payment obligation to the Collecting Entity is discharged when the funds are received in the Collection Account, and the User bears no risk of any delay or failure in the onward sweep to the Beneficiary Account. The receipt issued under clause 8.2 is the User's evidence of payment.

4.6The Collection Account. PayNow funds pass through a Collection Account held with the Payment Partner in the name of IBASE within that partner's collection framework. The account is an operating vehicle for the solution and is nominally in our name only. We cannot operate it except by the automated server-to-server instructions described in clause 4.1(f); no person at Qornerstone or IBASE can initiate, alter or release a payment from it manually. Funds in it are held for the account of the relevant Collecting Entity or property, are held separately from our own funds, are not applied for our own purposes, are not available to our creditors, are not subject to set-off against amounts owed to us by anyone, and confer no beneficial interest on us. The Payment Partner has confirmed in writing that it treats the funds as customers' money and has waived any right of set-off or combination it would otherwise have over the account. We will, on request by a Collecting Entity, disclose the identity of the Payment Partner that holds the Collection Account and make that written confirmation available for sighting.

4.7Settlement to the Beneficiary Account is made by the Payment Partner on the instruction described in clause 4.1(f), ordinarily at 11.00am on the day after the inward credit notification is received. Settlement timing depends on the Payment Partner and the banking system, and we give no warranty that it will occur at that time.

4.8Ledger tally and exception handling. We tally the incoming and outgoing payments ledgers daily so that every inward credit, less any Platform Fee, is matched to an outgoing payment from the Collection Account. Where an item does not tally, or where the Payment Partner has confirmed collection but the Beneficiary Account has not been credited, we will:

1. identify and record the exception on the day it is detected;
2. investigate and, where the cause lies with the Payment Partner or the banking system, raise it with the Payment Partner and pursue it on the Collecting Entity's behalf;
3. notify the Collecting Entity of the exception and keep it informed of progress; and
4. provide our transaction records, the inward credit notification and the sweeping instruction as evidence to support any claim.

4.9We will pursue an unresolved exception with the Payment Partner for as long as the Payment Partner permits a claim to remain open. Where a loss is caused by the Payment Partner or the banking system, the Collecting Entity's recourse is against that party, and clause 13.3(a) applies.

4.10Beneficiary Account nomination and changes. A Beneficiary Account is nominated, and any change to it made, only through our controlled procedure. That procedure requires a written application, verification against source documents such as a bank statement in the name of the account holder, and approval under a maker, checker and reviewer protocol in which three different individuals apply, check and approve the change. We may also require callback confirmation to a previously registered contact and written confirmation from the management corporation or owner. We maintain an audit trail of every nomination and change. We may decline or delay a change pending verification and are not liable for the resulting delay.

5.1A Platform Fee applies to each successfully processed Transaction. The fee depends on the nature of the Collecting Entity:

The Platform Fee is charged for the QuickPay service and applies to PayNow Transactions only. Card payments are a separate solution and are dealt with in section 6.

5.2The preferential Non-Profit Entity rate is offered on the basis of the Collecting Entity's status. A Collecting Entity must notify us if it ceases to qualify as a Non-Profit Entity, and we may require evidence of status. Where a managing agent collects on behalf of a Non-Profit Entity, the rate applicable is that of the entity for whose account the payment is collected, not that of the managing agent.

5.3Who pays. The Platform Fee is borne by one of three parties, in the following order:

1. the management corporation or other party for whose account the payment is collected, where it has executed a Qornerstone Subscription Agreement covering QuickPay for the property;
2. the managing agent or integrated facilities management company acting on that party's behalf, where it has executed a QuickPay Services Agreement covering the property; or
3. otherwise, the User. Where the User bears the Platform Fee, it is added to the amount payable and displayed before the User confirms the payment.

Where both (a) and (b) apply to the same property, the party named in the applicable agreement as bearing the fee does so, and where both agreements would apply, the QuickPay Services Agreement prevails.

5.4How the Platform Fee is collected. The method depends on who bears it:

1. where the managing agent or integrated facilities management company bears the fee under a QuickPay Services Agreement, the full Transaction amount is settled to the Beneficiary Account and the Platform Fees are invoiced to that party monthly in arrears;
2. where the management corporation or other party for whose account the payment is collected bears the fee under a Qornerstone Subscription Agreement, the Platform Fee is deducted from the Transaction amount before settlement to the Beneficiary Account. The payer's account is credited with the full amount paid, and the Platform Fee is posted to the finance ledger for the property as a fee expense; and
3. where the User bears the fee, the Platform Fee is added to the amount payable and displayed before the User confirms the payment. It is deducted from the amount received before the net Transaction amount is settled to the Beneficiary Account.

5.5We may vary the Platform Fee on 30 days' notice published on this page. A variation to the fee borne by a Collecting Entity is governed by its Qornerstone Subscription Agreement or QuickPay Services Agreement, as applicable.

5.6All fees are exclusive of GST, which is payable in addition at the prevailing rate.

6.1QuickPay is a PayNow solution. Credit and debit card payments are a separate solution and are not governed by these QuickPay Terms of Use. Nothing in these Terms, including the Platform Fee in section 5, applies to a card transaction.

6.2Card payments are governed by section 14 of the Qornerstone Platform Terms of Use. In summary: card processing is performed by a card acquiring partner appointed by us; the Collecting Entity must enter into a separate merchant agreement directly with that partner; that partner charges its own rate, currently 2.45% of transaction value plus SGD 0.15 per transaction; and a platform fee of 0.3% of transaction value is charged by us in addition under clause 9.8 of those terms.

6.3We are not the acquirer of card transactions and are not a party to the merchant agreement. Recourse in respect of card processing is against the card partner.

7.1What is a QuickPay payment. A QuickPay payment is a PayNow payment made using a QuickPay QR code generated by the Platform for a specific invoice, statement of account, booking charge or deposit. The QR code may be printed on a Qornerstone-generated invoice or statement of account, or displayed in the Qommunity+ application, a Qornerstone portal or another Qornerstone-linked online application. Each QuickPay QR code carries the amount payable, a unique transaction reference and the Collection Account as the beneficiary. A payment is a QuickPay payment only if it is made using that QR code without alteration. A User must not alter the amount, the transaction reference or the recipient details after scanning the QR code. A payment made in any other way, including a PayNow or bank transfer entered manually, is not a QuickPay payment and is dealt with under clause 7.2.

7.2Off-system payments. A payment made after altering those details, or made directly to the UEN or account details associated with the Collection Account instead of using the QuickPay QR code, is an off-system payment. It carries no transaction reference, so it cannot be matched to the User's account automatically.

7.3A User is responsible for ensuring that the payment relates to the correct transaction by checking the transaction details (such as facility booking), or unit number or such other details on the invoice or statement of account.

7.4Payment limits, daily caps and authentication requirements are set by the User, or the User's own bank or card issuer.

8.1Each Transaction carries a unique identifier generated by the Platform. Matching is performed against that identifier. Where it is absent or altered, automated matching will not occur.

8.2A receipt is created in Qornerstone and the relevant ledger updated once the Payment Partner confirms the payment. A receipt evidences the matching of a payment in the Platform. It does not by itself evidence cleared funds in the Beneficiary Account. Within a day, a system-generated email is sent to the User to confirm funds have been transferred to the Beneficiary Account.

8.3A daily reconciliation report is made available through the Platform identifying matched Transactions. Any failed, duplicated, missing or unmatched Transaction must be reported to us in writing within 5 Business Days of the Transaction date, or the date the person became aware or ought reasonably to have become aware of the discrepancy, whichever earlier. We are not liable for loss to the extent that it was caused or increased by a delay in reporting.

8.4We may make correcting entries in the Platform ledgers to reverse or re-post entries arising from a duplicate, mis-posted or reversed Transaction, and will notify the Collecting Entity where we do so.

8.5Refunds. QuickPay collects payments. It does not make them. There are three kinds of refund and none of them is processed through QuickPay:

1. Estate Credit refunds. Where a User holds a credit balance recorded as Estate Credit in the Qommunity+ application, the User may request a refund through the application by providing bank account details. That request is passed to the Collecting Entity, which decides on it and pays any refund itself as a manual payment outside QuickPay. Estate Credit is a record of funds held by the Collecting Entity, not funds held by us;
2. Erroneous collection. Where a payment was correctly made against an invoice that was itself issued in error, the Collecting Entity or its managing agent decides on the refund and pays it as a manual payment outside QuickPay; and
3. Off-system payments, which are dealt with under clause 7.2.

We do not hold funds from which a refund can be made, we do not use any refund facility of a Payment Partner, and we are not responsible for deciding, funding, calculating or paying a refund.

8.6No chargebacks. A QuickPay Transaction is a push payment: the User initiates it and authorises it with their own bank. There is no chargeback, direct debit recall or scheme reversal mechanism for a QuickPay Transaction. A settled Transaction can be unwound only by a separate payment made by the Collecting Entity under clause 8.5.

9.1We may suspend QuickPay for a User, a property or a Collecting Entity where we reasonably suspect fraud, money laundering or unauthorised access, where a Payment Partner, regulator or law enforcement authority requires it, where suspension is necessary to address a material security risk, where continued provision would breach applicable law, or where the Collecting Entity is in arrears. We will give as much notice as is reasonably practicable and restore service promptly once the cause is resolved.

10.1Section 11 of the Qornerstone Platform Terms of Use applies to Personal Data processed through QuickPay. This section adds to it.

10.2To process a Transaction we collect and use the payer's name, the unit and property identifiers, contact details, the invoice or account reference, the transaction identifier, amount, date and status, and the payer name and bank reference returned by the Payment Partner.

10.3We disclose that data to the relevant Payment Partner and to the Collecting Entity for the purposes of processing, settling, matching and receipting the payment, and to a regulator or law enforcement authority where required by law.

10.4Roles. The Collecting Entity is the organisation responsible under the PDPA for the invoice, account and unit records to which a payment relates. We process that data only on the Collecting Entity's behalf and on its instructions, and act as its data intermediary in doing so. We act as an organisation in our own right only in respect of a User's own registration and account data, as described in the Qornerstone Privacy Policy.

10.5The Payment Partner receives payment data from us in its capacity as the licensed payment processor. It handles that data as an organisation in its own right under the PDPA and under the regulatory obligations applying to it, and not as our data intermediary. The Payment Partner determines its own purposes and means of processing that data, and its own terms and privacy notice govern its handling of it. We do not instruct the Payment Partner in relation to that data and we are not responsible for its collection, use or disclosure of it.

10.6We retain Transaction records for 5 years from the date of the Transaction for accounting, tax and regulatory purposes.

11.1QuickPay must not be used to make or receive a payment for an unlawful purpose, for a sanctioned person, or in connection with money laundering or terrorism financing.

11.2We and our Payment Partners may screen, delay, decline, freeze or report a Transaction where required by law or by a Payment Partner's own compliance requirements, and may be prohibited from telling a User or a Collecting Entity the reason.

11.3Users and Collecting Entities must provide information we or a Payment Partner reasonably require for customer due diligence, sanctions screening, fraud investigation or regulatory reporting.

12.1A Collecting Entity indemnifies us against all losses, liabilities, fines, penalties and reasonable costs arising from:

1. its lack of authority to collect payments for a property enrolled in QuickPay,
2. incorrect, incomplete or unauthorised Beneficiary Account details provided by or for it,
3. any claim by a User, an owner or a management corporation arising from its own collection activities, invoices or communications, other than to the extent caused by our breach,
4. its breach of the PDPA, and
5. fraud or wilful misconduct of its personnel.

12.2We indemnify a Collecting Entity against all losses, liabilities, fines, penalties and reasonable costs arising from:

1. a claim that QuickPay, used in accordance with these Terms, infringes a third party's Intellectual Property Rights,
2. our breach of section 9 or of the PDPA in our capacity as data intermediary, and
3. fraud or wilful misconduct of our personnel.

12.3Clauses 15.3 to 15.5 of the Qornerstone Platform Terms of Use apply to these indemnities.

13.1Nothing in these Terms excludes or limits liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, or for any liability that cannot lawfully be excluded.

13.2Subject to clause 13.1, we are not liable for indirect or consequential loss, or for loss of profit, revenue, anticipated savings, business, goodwill or reputation, whether direct or indirect.

13.3Subject to clause 13.1, we are not liable for:

1. any act, omission, delay, failure, error or insolvency of a Payment Partner, a beneficiary bank, the PayNow scheme or the banking system;
2. late payment interest, penalties or administrative charges imposed by a third party following a failed, delayed or unmatched Transaction;
3. loss arising from payment details entered or altered incorrectly, including off-system payments and incorrect Beneficiary Account details;
4. loss to the extent caused or increased by a failure to report within the period in clause 8.3; or
5. failure or unavailability of internet, telecommunications or third party infrastructure outside our reasonable control.

13.4Subject to clauses 13.1 to 13.3, our total aggregate liability in respect of QuickPay is subject to a maximum of whichever of the following is the lower:

If that limit is held unenforceable, liability is capped at the amount of the Transaction. This limit applies whether the claimant is a User, a Collecting Entity or a Subscriber, and whether or not the claimant holds a licence. It is separate from, and is not aggregated with, the limit that applies to the Qornerstone software under clause 16.4B of the Qornerstone Platform Terms of Use. Clause 16.4C of those terms sets out this limit.

13.5No claim may be brought more than 12 months after the claimant became aware, or ought reasonably to have become aware, of the facts giving rise to it.

14.1We may update these Terms. The current version is published at qornerstone.com/quickpay-terms with its effective date. Material changes affecting a Collecting Entity are notified under its QuickPay Services Agreement. Continued use after the effective date constitutes acceptance.

14.2These Terms are governed by the laws of Singapore.

14.3Disputes with a Collecting Entity are resolved under clause 23 of the Qornerstone Platform Terms of Use. Disputes with a User are subject to the non-exclusive jurisdiction of the Singapore courts.