Payment Policy

Payment Policy

1. The Role of Payment in the Transaction Process

Within the transaction process, making a payment serves as a “process initiation” action.
Before payment is completed, the order is considered only as a pending record, and relevant fulfillment processes have not yet begun.

The order will proceed to subsequent processing stages only when the system recognizes a valid payment result.
This determination is based on transaction information returned by the payment provider, not solely on the page display.

2. Available Payment Methods

Currently, the payment options provided on the page are limited to the following card types:

• Visa

• MasterCard

Payment tools not displayed on the page are generally not supported. Availability is determined by the real-time display on the checkout page.

3. Scope of Payment Information Use and Retention Principles

Card number, expiry date, and security verification information used during payment is only used to validate the current transaction.
After the transaction is completed, such information will not be stored in the order record, account data, or any other accessible location.

The system does not maintain any form of payment information archive and such data will not be used for future charges or calls.

4. Presentation Logic of Order Amount Before Payment

Before completing payment, the checkout page presents a consolidated view of the order amount, which generally includes:

• Product price

• Applicable shipping fee (as displayed)

The product price already includes all necessary charges for the order, such as:

• Australian GST (10%)

Once payment is completed, the order amount will not be adjusted due to taxes or routine customs duties.

5. Understanding Payment Exceptions

During payment, if verification is incomplete, the page remains static, or the status update is delayed, the validity of payment should be determined primarily by the transaction result returned by the payment provider.

Page status changes may lag behind actual processing, so understanding should be based on both the payment record and the order page display.

6. Responsibility Statement and Process Boundary

In the payment process, the following situations are generally considered objective operational contexts, and do not serve as sole grounds for assigning responsibility:

• Risk checks or verification pace of the payment platform

• Processing differences between issuing banks for transaction confirmation

• Delays during page redirects or refreshes

• Status changes caused by multiple payment attempts

This explanation is intended to clarify the operational context of the payment process and does not constitute any pre-judgment of transaction outcomes.