This is a policy template for a merchant and its customers, not a sales contract between Aster and visitors to this website.
Store policies are templates for merchants to adapt and review against their actual seller, products and sales markets.
1. Payee and payment providers
The seller and payee merchant is example, statement descriptor example, PSP example, PSP policy link https://example.com. These placeholders must be replaced with the actual integration details. Aster software does not hold this store’s consumer funds; the merchant receives settlement from its PSP. Payment for goods is separate from the merchant’s SaaS subscription to Aster and does not enroll you in that subscription.
2. Total price and charge authorization
Before payment, item prices, discounts, shipping, applicable taxes and the total are displayed with a confirmation action indicating payment obligation. Add-ons require active choices, not preselected extra charges. If a product is a recurring subscription, its amount per period, frequency, start, renewal, term and cancellation path require separate clear disclosure and authorization. An ordinary product order does not contain an implied recurring-charge mandate.
3. Multiple currencies and conversion
Available transaction currencies are example. Final charge currency and amount are consistent across checkout, payment confirmation and order records. Browsing estimates identify their indicative nature and source or reference time. Currency precision and rounding must not conceal extra fees, and totals must be reconcilable. Issuer conversion and foreign-transaction fees follow issuer rules, so we cannot guarantee the bank’s domestic-currency debit, but this does not permit changing the accepted merchant transaction price.
4. Verification, capture and order status
The PSP or issuer may require additional verification such as 3-D Secure or wallet confirmation. Authorization does not necessarily mean capture, and the merchant must distinguish pending, authorized, captured and refunded states. A completion page is not the sole evidence of payment; verified events and reconciliation establish status. If a page fails, contact a person with the order reference. Repeated clicks must not cause duplicate billing, and suspected duplicates require prompt investigation and correction.
5. Payment data and security
Full PANs, CVVs and other sensitive authentication data are handled by the actual PSP’s secure payment flow, not collected or retained by the merchant or Aster through their own fields, logs, email or AI support. Systems retain only tokens, references, payment-method summaries and status needed for transactions and after-sales service. Do not comply with requests to send CVVs, one-time passcodes, passwords or private keys through support; contact security@example.com to verify.
6. Refunds and currency differences
Refunds are reviewed by the merchant and executed through an authorized process under the returns policy, normally to the original method in the original transaction currency. The merchant refund reflects the amount legally owed. Different bank conversion dates may create a domestic-currency difference that the relevant provider must explain, so identical domestic-currency posting cannot be promised. Refund initiation and actual bank posting are distinct. Estimated posting time is example, to be confirmed with the actual PSP, while statutory initiation or completion duties prevail.
7. Taxes and invoices
Tax type, registration, invoice issuer and tax-inclusive pricing must reflect the actual seller, product, customer status and market. Sales tax, VAT/GST, import duties and clearance fees are distinct. You may supply required invoice information and contact support@example.com for corrections. Platform calculations or AI suggestions are not tax rulings. The merchant verifies registrations, rates, exemptions and filings and cannot shift all consequences of its mistakes to consumers.
8. Disputes and contact
For an unrecognized charge, payment failure or suspected unauthorized transaction, contact support@example.com or your payment institution. The merchant may request necessary order evidence but not full card details and must not obstruct a timely bank dispute. Amounts already reimbursed elsewhere may be checked to prevent duplicate payment without indefinitely freezing unrelated refunds. Version: draft-2026-10-10. Operative date: example. This policy must align with actual PSP terms and consumer rights.