GSMXCODE

1. Scope & Digital Services

1.1 Services Covered

This Policy applies to eligible products and services advertised, ordered, or made available through the GSMXCODE website, where this Policy is presented at checkout or otherwise incorporated into the transaction. The seller or service provider for each purchase is the person or entity identified in the pre-purchase disclosures and the order confirmation or receipt. Depending on the product catalogue, covered offerings may include:

• SaaS subscriptions;
• API subscriptions;
• defined API usage packages;
• diagnostic and device-information services;
• authorized technical, server-based, remote, and diagnostic services;
• developer tools, web utilities, and digital business solutions;
• software, software licences, activation codes, licence keys, and digital downloads;
• game, gift-card, and social-media products where offered; and
• any other product or service specifically identified at checkout.

1.2 Digital Delivery

A digital product is ordinarily treated as delivered when the purchased file, key, code, access right, report, subscription, or other contracted output is made available to the Customer in the manner disclosed at checkout. A technical or server-based service is ordinarily treated as performed when the disclosed operation is completed or the authorized request is submitted to the relevant processing channel, as applicable to that product. A payment receipt alone is not proof that a service was successfully delivered. A failed, rejected, or materially incomplete operation may be reviewed under Section 3 and Section 7.

1.3 Order Records

Transaction and technical records may be used to review cancellations and refund requests, including the order-created timestamp, payment status, cancellation request timestamp, order status, delivery or activation event, supplier response, subscription activity, API consumption, and relevant support communications. Records will be handled in accordance with the Privacy Policy and applicable law. Customers should provide only information reasonably needed to investigate the request and should avoid sending passwords, full payment-card numbers, or unrelated sensitive information.

2. Cancellation

2.1 Standard 120-Second Order Cancellation Window

All orders may be cancelled within one hundred and twenty (120) seconds (two minutes) after they are placed. The period begins at the order-created timestamp recorded by the Platform, not when payment later settles, an email is delivered, or a confirmation message is opened. A cancellation request is timely when the Platform records it, or an authorised support channel receives and records it, before the 120-second period expires.

To cancel, use the cancellation control in the Customer dashboard or order history when available. If that control is unavailable or fails, contact [email protected] through email or the Platform's live chat and include the order number and a clear cancellation request. Keep the resulting confirmation or ticket reference. If a technical failure prevents the request from being recorded, report it promptly and provide reasonably available evidence of the attempt; the request will be reviewed fairly.

An order successfully cancelled within this window will be cancelled without a cancellation penalty. If payment has been captured, the amount charged for the cancelled order will be refunded to the original payment method, subject to applicable law and payment-provider processing. If the payment is only authorised and has not been captured, the authorisation may instead be voided or released. The time it takes for funds to appear is controlled in part by the bank, card network, or payment provider.

To honour this window, the order-processing workflow must hold ordinary fulfilment for 120 seconds after order placement before a licence key, download, account credit, API or supplier request, remote-service instruction, or other irreversible action is released. A technical mistake or premature supplier submission does not, by itself, remove any refund or other right that applicable law makes mandatory.

2.2 Requests After the 120-Second Window

After the 120-second window expires, an order may no longer be cancellable automatically if fulfilment has begun, a key or digital output has been disclosed, usage has been consumed, or the request has entered irreversible third-party processing. If fulfilment has not begun, a Customer may still ask support to cancel the order; approval depends on the product, supplier status, disclosed product terms, and applicable law. This section does not prevent a refund request for duplicate or erroneous charges, non-delivery, a materially non-conforming product or service, or any other remedy required by law.

2.3 Subscription Cancellation

The 120-second window applies to cancellation of the initial subscription order as well as to other eligible orders. After that window, Customers may cancel recurring subscriptions through the account or subscription-management controls to stop future renewal. Unless a product page or applicable law provides otherwise, stopping renewal does not by itself refund a billing period that has already begun or been used.

2.4 Mandatory Withdrawal and Consumer Rights

The 120-second window is an additional order-cancellation policy; it does not replace or shorten any mandatory statutory withdrawal, cancellation, conformity, warranty, refund, or other consumer right. Where the law requires specific consent or acknowledgement before digital content or a service is supplied immediately, that consent and acknowledgement must be obtained through the checkout process and recorded as required by law.

3. Refund Eligibility

3.1 Unfulfilled Services

A Customer may be eligible for a refund where the seller or service provider identified for the transaction has charged for a Service that was not successfully delivered or fulfilled and cannot reasonably complete it within the applicable delivery terms.

3.2 Duplicate or Erroneous Charges

Refunds may be issued for verified:

• duplicate transactions;
• incorrect billing;
• system-generated duplicate orders;
• charges for a transaction that failed to create the corresponding Service; or
• other documented payment-processing errors.

3.3 Materially Non-Conforming Service

A Customer may request a refund or other remedy where a delivered product or Service materially fails to conform to the functionality or service outcome expressly described on its product page and the issue cannot reasonably be corrected.

3.4 Refund Review

Refund requests may be evaluated against the order record, product description, delivery record, subscription status, API usage, payment record, and relevant technical information.

4. API Usage & Digital Consumption

4.1 Prepaid API Usage

Defined API Usage Packages provide a specified quantity of API consumption capacity for the applicable API Service.

API usage is considered consumed when authenticated requests are submitted and processed by the relevant API infrastructure, in accordance with the applicable API pricing and usage rules. Usage capacity is service-specific and is not a cash-equivalent balance.

4.2 Consumed Usage

API usage that has already been consumed is generally non-refundable because the underlying digital Service has already been provided.

4.3 Unused Usage

Where a refund is otherwise eligible, the responsible service provider may consider the unused portion of an API Usage Package, subject to the applicable product terms, payment-provider requirements, and applicable law.

4.4 Usage Verification

The responsible service provider may use server-side API logs, authenticated request records, timestamps, customer account information, and other technical records to determine the amount of Service consumed.

4.5 Platform Credits or Service Balances, Where Offered

Any site credit, service balance, or usage balance may be used only as described at the point of purchase and in the applicable product terms. Such a balance must not be assumed to be cash or redeemable for cash merely because it is displayed in an account. If a payment is refunded, the refund route will be determined by the payment method, the product-specific terms, payment-provider rules, and applicable law. A balance funded by an actual payment will not be forfeited, converted, or withheld in a manner that overrides a mandatory refund or consumer-protection right. Any separate credit or balance terms disclosed at checkout apply only to the extent consistent with this Policy and applicable law.

5. Subscriptions

5.1 Recurring Billing

Subscription Services renew automatically according to the billing interval shown during checkout unless cancelled before the next billing date.

5.2 Cancellation

Cancellation normally prevents future renewal but does not automatically refund the current billing period.

5.3 Accidental Renewal

If a Customer believes a subscription renewed unintentionally, the Customer should contact support promptly. The responsible service provider may review subscription history, usage, and billing information and provide an appropriate remedy where warranted.

5.4 Service Failure

If a paid subscription becomes materially unavailable due to a technical issue attributable to the responsible service provider, that provider may provide an extension, account credit, partial refund, or other reasonable remedy, depending on the circumstances and subject to applicable law.

6. Non-Refundable Situations

Subject to the 120-second cancellation right in Section 2, applicable law, and the exceptions described elsewhere in this Policy, the following are generally not refundable once validly delivered, activated, redeemed, or consumed:

• API usage that has already been consumed;
• software or digital content that has been successfully delivered and is functioning as described;
• subscription periods that have already started and been materially used;
• a digital key, activation code, game code, gift card, or similar code that has been revealed, activated, redeemed, or used, except where a refund is required by law or the code was defective or not as described;
• a third-party service request that was correctly performed or irreversibly processed in accordance with the product description, subject to any mandatory statutory remedy;
• services completed in accordance with the applicable product description, eligibility requirements, and authorization requirements;
• purchases made using incorrect customer-provided information where the Service was correctly delivered according to that information;
• duplicate purchases made intentionally or through customer error where both purchases were properly delivered; and
• purchases made after the Customer reviewed the applicable product requirements and then determined that the Service was not suitable for a use case that was not supported or advertised.

7. Defective or Non-Conforming Services

7.1 Verification

Before deciding a claim concerning a technical issue, the support team may request reasonable, proportionate information needed to verify the order, delivery status, or reported failure. Evidence requirements will depend on the product and the type of issue; a continuous video recording is not a universal prerequisite where other reasonable evidence can establish the relevant facts.

Depending on the Service, this may include:

• order number;
• account information;
• timestamps;
• screenshots;
• error messages;
• API request/response information;
• relevant technical logs; or
• other information reasonably necessary to determine whether the Service conformed to its description.

7.2 Resolution Options

Where a defect or material non-conformity is verified, The responsible service provider may, depending on the circumstances:

• correct the issue;
• re-provision the Service;
• replace the affected digital product;
• extend the Service period;
• issue a partial refund; or
• issue a full refund.

7.3 Customer-Provided Information

For device-related, carrier-authorised, remote, server-based, or other third-party-dependent services, performance may depend on supplier systems, manufacturer or carrier databases, external eligibility results, network access, and conditions outside the support team's direct control. A service correctly performed according to the description and the information available at the time is not automatically refundable solely because an external provider later changes a record, policy, or result. However, where the paid service was not delivered, materially differed from its description, or is subject to a mandatory legal remedy, this paragraph does not remove the Customer's right to request an appropriate remedy.

A refund will not generally be due solely because the Customer submitted materially incorrect or incomplete information, selected an incompatible product, lacked required authority over the device or account, or requested a use that was not disclosed as supported, if the service was otherwise properly supplied as ordered. This does not apply where a remedy is required by applicable law or the order was not performed as described.

7.4 Misuse, Unauthorised Requests, and Policy Violations

A Customer is responsible for providing accurate order details and for having the permissions and lawful authority required for any device, account, identifier, data, or third-party service involved. A refund will not generally be available merely because access is suspended or a service is stopped after credible evidence of fraud, unauthorised use, prohibited activity, or materially false information supplied by the Customer. The provider may suspend an order or account while investigating a genuine security or compliance concern, but it will assess any unfulfilled portion and will not use this clause to avoid a refund or remedy that applicable law requires.

8. Payment Disputes & Chargebacks

8.1 Contact Support

Customers are welcome to contact [email protected] before initiating a payment dispute so that a billing, cancellation, or fulfilment issue can be investigated. Contacting support first is encouraged, but it is not a prerequisite to exercising a lawful right to dispute a transaction with a bank, card issuer, payment provider, or competent authority.

8.2 No Restriction of Statutory Rights

Contacting support first does not waive or restrict any legal right or payment-provider dispute right available to the Customer.

8.3 Dispute Evidence

Where a payment dispute is initiated, the relevant service provider may submit transaction and fulfilment evidence to the payment processor, acquiring bank, card network, or payment provider in accordance with applicable law, privacy obligations, and the provider's dispute procedures. This Policy does not impose an automatic fixed chargeback penalty, waive a Customer's dispute rights, or presume that every disputed payment is fraudulent. Where there is credible evidence of fraud or abuse, access may be restricted while the matter is reviewed, and any further recovery action must have a lawful basis.

Such evidence may include:

• order information;
• customer account records;
• payment confirmation;
• acceptance of the applicable Terms and Refund Policy;
• delivery records;
• subscription records;
• API usage or access records;
• service-delivery, eligibility, or authorization records;
• customer communications; and
• refund or cancellation history.

9. Refund Processing

9.1 Request Submission

Refund requests should be submitted to: [email protected]

Please include the order number, account email, description of the issue, and any relevant evidence.

9.2 Review

The support team aims to review complete refund requests within 3–5 business days. This is a review target, not a guarantee of payment-provider posting time or the outcome of a request.

Additional time may be required where the request requires technical investigation, third-party verification, or payment-provider review.

9.3 Refund Destination

Where an original-payment refund is approved, The responsible service provider will generally submit an approved refund through the payment method or payment provider used for the original transaction.

For security and fraud-prevention reasons, refunds are normally sent to the original payment method. An alternative route may be used only where the original route is unavailable, the payment provider supports it, and the alternative is legally permitted. A refund will not be converted into service credit in place of a monetary refund where applicable law requires payment back to the Customer.

9.4 Processing Time

After an approved original-payment refund is submitted, the actual posting time depends on the applicable payment processor, card network, bank, or payment provider.

9.5 Service Credits

Where appropriate and permitted by the applicable product terms, the responsible service provider may offer a replacement Service or service-specific usage adjustment instead of a monetary refund. Any such alternative is limited to the relevant Service, is not transferable or redeemable for cash unless the product terms or law provide otherwise, and will not override a mandatory refund right.

10. Legal Exceptions

10.1 Mandatory Rights

Nothing in this Refund Policy excludes, restricts, or waives any right or remedy that cannot legally be excluded or waived.

10.2 Digital Consumer Rights

Where a Customer's jurisdiction provides mandatory cancellation, withdrawal, conformity, warranty, or refund protections for digital content or services, those protections apply to the extent required by law. In some jurisdictions, immediate digital supply may require the Customer's prior express consent and acknowledgement of the effect on a withdrawal right, and the provider may be required to confirm that consent. A general acceptance of this Policy must not be treated as a substitute for any separate consent, acknowledgement, or disclosure legally required at checkout.

10.3 Payment Provider Requirements

Refunds may also be subject to operational requirements imposed by payment processors, acquiring institutions, card networks, banks, or other payment providers.

11. Contact