Payment Policy

The CoreSphere Technologies is a sole proprietorship business based in Mumbai, Maharashtra, India. We provide custom software, website development, SaaS, WaaS, automation, artificial intelligence-enabled solutions, implementation, maintenance, support and related digital services.

This Policy should be read together with our Terms & Conditions, Privacy Policy, Refund & Cancellation Policy, Service Delivery Policy, and the applicable quotation, proposal, invoice, subscription plan or product-specific terms.

1. Accepted Payment Methods

Depending on availability and the nature of the transaction, payments may be accepted through:

• Bank transfer, NEFT, RTGS or IMPS.
• UPI transfer or merchant UPI QR.
• Authorised payment links.
• SmartHub Vyapar merchant payment facilities.
• SmartGATEWAY or another authorised website or application payment gateway.
• Debit cards, credit cards, NetBanking, wallets or other supported payment modes.
• Another method expressly communicated by us through an official quotation, invoice, email or website page.

The payment methods displayed at checkout or stated in the invoice will apply to that transaction.

2. Currency

Unless otherwise stated in writing, prices and payments are quoted and collected in Indian Rupees (INR).

Where an international currency is accepted, the customer may be responsible for foreign-exchange conversion, correspondent-bank charges, card-issuer charges, taxes and other fees imposed by the relevant financial institution.

3. Quotations, Invoices and Payment References

Customers should make payments only against an official quotation, proposal, invoice, subscription plan, payment link or written instruction issued by The CoreSphere Technologies.

The customer is responsible for checking the following before payment:

• Business name and authorised payment recipient.
• Invoice, quotation or subscription reference.
• Amount, currency, taxes and due date.
• Purpose of payment and applicable milestone or plan.
• Payment link domain, QR details or beneficiary details.

Customers should mention the correct invoice, quotation, subscription or project reference wherever the payment method allows.

4. Advance, Milestone and Final Payments

Custom services may require an advance, milestone payments and a final payment according to the accepted proposal or invoice.

• Work may begin only after the required advance payment is received and verified.
• Further work, deployment, handover or access may depend on completion of the applicable milestone payment.
• Final deliverables, credentials, source files or production access may be withheld until all due payments are received, unless otherwise agreed in writing.
• Overdue payments may result in delayed delivery, suspension of work, restricted access or revised timelines.

5. SaaS and WaaS Subscription Payments

SaaS and WaaS plans may be billed monthly, annually, per user, per tenant, by usage, by implementation stage or under another model displayed in the relevant product or proposal.

• Subscription access is activated after successful payment and any required verification.
• Renewal dates, billing periods and plan limits will be shown in the applicable product, invoice or subscription communication.
• Failure to make a renewal payment may result in suspension, downgrade, restricted access or termination under the product-specific terms.
• Taxes, implementation, migration, messaging, AI usage, storage, integrations or third-party charges may be billed separately where applicable.

6. Taxes and Statutory Charges

Prices may be exclusive of applicable taxes, duties, levies, bank charges or statutory fees unless expressly stated otherwise.

Applicable taxes will be disclosed in the quotation, invoice or checkout where required. Customers are responsible for providing accurate billing and tax information.

Where tax deduction at source or another statutory deduction applies, the customer must provide the required certificate or evidence within the applicable legal period.

7. Payment Confirmation

A payment is treated as successfully received only after it is credited and confirmed in our records.

A payment screenshot, initiated-transfer status, pending bank message or customer-side confirmation does not by itself constitute final settlement.

After successful reconciliation, we may issue a receipt, invoice update, subscription confirmation, activation message or other acknowledgement.

8. Payment Security

Online payments may be processed by authorised banks, payment gateways, merchant-acquiring partners, card networks, UPI systems, wallets or other regulated payment service providers.

The CoreSphere Technologies does not directly request or store your UPI PIN, card PIN, complete card number, CVV, NetBanking password or one-time password.

Customers must never share these confidential credentials with us, our staff, support personnel or anyone claiming to represent us.

Payment pages may use security controls such as encryption, authentication, risk checks, transaction limits, tokenisation or fraud monitoring provided by the relevant bank or payment processor.

9. SmartHub Vyapar, Merchant UPI QR and Payment Links

We may use SmartHub Vyapar, merchant UPI QR or authorised payment links to collect payments for quotations, invoices, subscriptions, project advances, milestone payments, renewals or other approved business transactions.

• Customers should verify the merchant or business name displayed before authorising payment.
• A payment link should be opened only from an official communication or website page associated with The CoreSphere Technologies.
• UPI collect requests should be carefully reviewed before approval.
• Customers must confirm the amount, merchant name and purpose before entering their UPI PIN.
• Payment links and QR codes must not be copied or reused for an unrelated transaction unless specifically authorised.

10. SmartGATEWAY and Website Payments

SmartGATEWAY or another approved payment gateway may be used to accept payments through our website, product websites, SaaS platforms or applications.

The available payment modes, transaction limits, authentication requirements, service availability and processing time may be determined by the payment provider, issuing bank, card network, UPI system or applicable regulation.

Gateway approval, onboarding, uptime and acceptance of a particular payment method remain subject to the relevant provider’s policies and systems.

11. Failed Transactions

A transaction may fail because of insufficient balance, incorrect credentials, authentication failure, bank decline, network interruption, transaction limit, payment-provider error or another technical issue.

• If the transaction fails and no amount is debited, the customer may attempt payment again using an available method.
• If the transaction fails but an amount is debited, the customer should first verify the final status with their bank or payment provider.
• Where the amount was not credited to us, reversal is generally handled by the bank or payment provider.
• Where the amount was credited to us despite a failure message, we will verify and reconcile the transaction.

12. Pending Transactions

A pending transaction is not treated as final until the bank or payment provider confirms success or failure.

Customers should avoid making repeated payment attempts while the original transaction remains pending unless advised by their bank or by us after verification.

13. Duplicate Payments

If the same invoice, quotation, subscription or service is paid more than once and both payments are successfully received, the duplicate payment will be reviewed.

After verification, the duplicate amount may be:

• Refunded to the original payment method; or
• Adjusted against another valid invoice or future payment with the customer’s written approval.

14. Payment Successful but Service Not Activated

If payment is successfully received but the related subscription, workspace, account, licence or service is not activated within the communicated period, the customer should contact us with the transaction reference.

After verification, we will complete activation, correct the technical issue, adjust the payment or process an eligible refund according to our Refund & Cancellation Policy.

15. Recurring Payments and Mandates

Where recurring billing, AutoPay or an authorised mandate is available, the amount, frequency, billing cycle and cancellation method will be communicated during setup.

• The customer is responsible for ensuring that the payment method remains valid and sufficiently funded.
• A failed recurring debit may result in retry attempts, payment reminders, restricted access or suspension.
• Cancellation of a mandate stops future authorised debits after the cancellation becomes effective.
• Cancelling a mandate does not automatically refund a previous valid debit.

16. Refunds

Refund eligibility is governed by our Refund & Cancellation Policy and any applicable product-specific terms.

Approved refunds are ordinarily initiated to the original payment method within 7–10 working days after approval. The bank, card issuer, UPI provider, gateway or wallet may take additional time to credit the amount.

17. Chargebacks and Payment Disputes

Before initiating a chargeback or payment dispute, customers should contact us so that we can review the transaction, invoice, service status and supporting records.

Customers should provide the transaction reference, amount, date, invoice or quotation number and a clear explanation of the dispute.

Fraudulent, duplicate or unjustified chargebacks may result in suspension of services and recovery of applicable costs, subject to law and the rules of the relevant bank or payment provider.

18. Fraud Prevention and Verification

We or the payment provider may delay, decline, reverse, investigate or request additional verification for a transaction where fraud, identity misuse, unauthorised activity, inconsistent information or security risk is suspected.

Verification may include confirmation of customer identity, business details, billing details, transaction purpose, invoice reference or authorised-user status.

19. Unauthorised Payments

A customer who believes a payment was unauthorised should immediately contact their bank or payment provider and also inform us.

We will cooperate with reasonable verification and lawful investigation requests but cannot independently reverse a transaction that was not credited to us or that is controlled by another financial institution.

20. Payment Receipts and Records

Customers should retain invoices, receipts, transaction references and bank confirmations for their records.

We may retain limited transaction records such as amount, date, status, payment mode, invoice reference and provider transaction ID for reconciliation, accounting, support, fraud prevention, audit and legal compliance.

21. Prohibited Payment Conduct

Customers must not:

• Use stolen, unauthorised, fraudulent or unlawfully obtained payment credentials.
• Misrepresent the payer, customer, transaction purpose or billing details.
• Attempt to bypass payment authentication, security controls or transaction limits.
• Use a payment link, merchant QR or gateway for an unrelated or prohibited transaction.
• Initiate a knowingly false payment dispute or chargeback.

22. Third-Party Payment Provider Terms

Banks, payment gateways, card issuers, UPI providers, wallets and merchant-acquiring partners may apply their own terms, privacy policies, fees, eligibility conditions, limits, security checks and dispute processes.

We are not responsible for outages, declines, delays, reversals, policy changes or account restrictions caused by third-party payment systems outside our reasonable control.

23. Payment Support

For a payment issue, send an email with the subject line Payment Support and include:

• Customer name and business name.
• Registered email address and phone number.
• Invoice, quotation, subscription or project reference.
• Transaction reference, payment date, amount and payment mode.
• Description of the issue.
• Relevant screenshot with confidential credentials hidden.

Never send a UPI PIN, card PIN, CVV, OTP, NetBanking password or complete card details.

We aim to acknowledge genuine payment-support requests within two working days.

24. Changes to This Policy

We may update this Payment Policy to reflect changes in payment methods, provider requirements, products, services, legal obligations or business practices. The revised Policy will be published on this page with an updated effective date.