Payment Policy
Snap Matrix · Payment Policy · v1.0 · effective 29 July 2026
| Field | Value |
| Operator | Trexadoc OÜ |
| Company number | 17367549 |
| Registered office | Harju maakond, Tallinn, Kesklinna linnaosa, Pärnu mnt 20, 10141, Estonia |
| Trading name / brand | Snap Matrix |
| Website | https://snap-matrix.com |
| Contact email | info@snap-matrix.com |
| Support / complaints | info@snap-matrix.com |
| Governing law | Laws of the Republic of Estonia |
| Document version | v1.0 |
| Effective date | 29 July 2026 |
| Important: Snap Matrix offers one-off purchases only under this Policy. It does not automatically renew Token Packs or charge a subscription. The final amount, currency, product and immediate digital-supply terms are displayed before the customer confirms an Order. |
1. Scope and payment architecture
1.1 This Policy governs payment for Token Packs, paid photo content and any separately priced AI-generation transaction offered through Snap Matrix. It explains price presentation, authorisation, settlement, security, failed payments, refunds and disputes.
1.2 Trexadoc OÜ is the merchant contracting with the customer. Card processing and related authentication are performed through the regulated third-party payment provider identified in the checkout or transaction confirmation (Payment Provider).
1.3 The Payment Provider may act as an independent controller for payment-compliance, fraud-prevention and network functions. Its own terms and privacy notice apply to those activities; Snap Matrix remains responsible for the merchant obligations described here.
1.4 The Terms and Conditions, Refund Policy and Digital Product Fulfilment Policy form part of the same transaction framework. Mandatory consumer and payment rights prevail over an inconsistent contractual limitation.
2. Products and charging model
2.1 A Token Pack is a one-time purchase of a stated quantity of service credits. Tokens may be used only within Snap Matrix for eligible generation or content-access functions and have no cash-redemption, investment, transfer or stored-value function.
2.2 Paid photo content may be sold as a discrete entitlement to view or download the described digital file. A generation transaction may consume Tokens according to the cost displayed before submission or, where clearly offered, be charged as a separate one-off Order.
2.3 Snap Matrix does not offer subscription billing under this version of the Service. Saving an Account, keeping a payment credential with a Payment Provider or retaining unused Tokens does not authorise recurring charges.
2.4 A new recurring product may be introduced only through an updated checkout and terms that clearly state frequency, renewal amount or calculation, cancellation method and any trial conversion before the customer consents.
3. Prices, currency and taxes
3.1 Prices are displayed in EUR unless the checkout expressly states another transaction currency. The final confirmation shows the product, quantity, gross amount, applicable value-added tax or other mandatory charge, and any discount.
3.2 Consumer-facing prices include applicable value-added tax where required. If the customer’s status or location affects tax treatment, the checkout may request country, billing address, tax number or other information needed to calculate the correct amount.
3.3 A bank or card issuer may convert the transaction into the customer’s account currency and charge its own fee. Such conversion and issuer fee are not imposed by Snap Matrix and may differ from an indicative display.
3.4 A clear pricing error may be corrected before acceptance. Snap Matrix will not silently charge a higher amount; it will reject or cancel the affected Order and invite a new confirmation at the corrected price.
4. Accepted payment methods
4.1 The checkout may accept Visa, Mastercard and other cards or methods displayed at the time of purchase. Availability can vary by country, device, risk profile, currency and Payment Provider capability.
4.2 Displaying a logo does not guarantee that every card or account under that scheme will be accepted. The issuer and Payment Provider may apply eligibility, authentication, limit or geographic controls.
4.3 Snap Matrix does not accept cash, cheques, banknotes sent by post, cryptocurrency, unlicensed money transfer, or Tokens as payment for Tokens. A promotional code is not a payment method and can be used only under its stated conditions.
4.4 A payment method may be removed or temporarily disabled for security, compliance, technical or commercial reasons without affecting a completed Order or an accrued refund right.
5. Checkout and order confirmation
5.1 Before the customer commits to payment, the checkout presents the product, Token quantity or content entitlement, total price, currency, applicable taxes, key restrictions and immediate digital-supply consent where relevant.
5.2 The customer must review the Order and correct input errors before selecting the final payment action. The payment button or equivalent control clearly indicates that the action creates an obligation to pay.
5.3 Submitting the checkout is an offer to purchase. Acceptance occurs when Snap Matrix sends the Order confirmation or makes the paid entitlement available after successful payment, whichever occurs first, unless mandatory law requires another point.
5.4 The confirmation is sent electronically and includes or links to the contract information required for the digital purchase. The customer should retain it with the Order ID and payment record.
6. Authorisation, authentication and settlement
6.1 The Payment Provider sends the transaction to the relevant network and issuer for authorisation. Authorisation confirms that the payment may proceed at that time; it does not always mean final settlement has occurred.
6.2 Strong customer authentication, a one-time passcode, banking-app confirmation or another issuer challenge may be required. The customer must complete the challenge through the issuer’s secure interface, not disclose the code to Snap Matrix support.
6.3 An issuer may place a temporary authorisation hold. If the Order is declined or cancelled before capture, the issuer controls when that hold disappears. A released hold is not a refund because the amount was not settled to Snap Matrix.
6.4 Digital fulfilment begins after the checkout reports a successful payment or another approved status. Snap Matrix may defer fulfilment for up to twenty-four hours while resolving an inconsistent, duplicated or high-risk result disclosed by the Payment Provider.
7. Payment lifecycle matrix
7.1 The following lifecycle separates states that commonly appear similar on a bank statement. The actual issuer wording may vary.
| State | Meaning | Customer impact | Snap Matrix action |
| Initiated | Checkout submitted; no final result | No entitlement yet | Wait for provider response; prevent duplicate submission |
| Authentication required | Issuer challenge pending | Complete secure issuer step | Keep Order pending for a limited period |
| Authorised | Issuer approved and may reserve funds | Pending or reserved amount may appear | Proceed to capture and fulfilment subject to checks |
| Captured / paid | Payment accepted for settlement | Charge becomes payable | Issue confirmation and fulfil digital product |
| Declined | Issuer or provider refused transaction | No completed purchase | Do not fulfil; show retry guidance |
| Voided | Authorisation cancelled before settlement | Hold may remain temporarily | No refund initiated; provider releases authorisation |
| Refunded | Merchant initiated return after capture | Credit posts under issuer timing | Reverse entitlement as applicable |
| Chargeback / disputed | Issuer dispute process opened | Provisional credit may apply | Preserve evidence; suspend related benefit where lawful |
8. Merchant descriptor and receipts
8.1 The card statement should ordinarily show the descriptor “SNAP MATRIX” or a recognisable variant containing that name. The issuer may abbreviate, add a location or display the Payment Provider’s formatting.
8.2 A receipt or Order confirmation identifies Trexadoc OÜ, the Snap Matrix brand, Order date, product, amount, currency, taxes and Order reference. It may also show the payment method type and masked final digits.
8.3 A customer who does not recognise the descriptor should compare the statement date and amount with Account purchases and contact support before initiating a dispute where safe to do so.
8.4 Snap Matrix does not put sensitive prompts, generated content or full card data on the statement descriptor or ordinary receipt.
9. Card-data security
9.1 Card entry is routed through the Payment Provider’s hosted or tokenised payment interface. Snap Matrix does not require the customer to send a complete primary account number, card verification code or authentication password to its support team.
9.2 Snap Matrix ordinarily receives a provider token, masked card details, scheme, country, authentication and risk results, and transaction references needed to fulfil and support the Order. A token is not usable as a general card number.
9.3 Payment security controls include transport encryption, access control, logging, fraud rules, provider due diligence, vulnerability management and minimisation of cardholder data. The applicable Payment Card Industry Data Security Standard responsibilities are allocated with the Payment Provider.
9.4 Customers must use a payment method they are authorised to use and must protect devices, banking credentials and Account access. Suspected compromise should be reported immediately to the issuer and Snap Matrix.
10. Saved payment credentials and one-click use
10.1 Where the checkout offers credential saving, the Payment Provider stores the underlying credential and returns a reusable payment token. Snap Matrix may display masked information so the customer can recognise and remove the saved method.
10.2 Saving a method is optional and does not create recurring billing. A later one-click purchase still requires an affirmative Order action and may require renewed issuer authentication.
10.3 The customer can remove a saved method through the Account or Payment Provider interface where available. Removal prevents future merchant-initiated access to that token but does not delete transaction records required for accounting, disputes or compliance.
10.4 A Payment Provider may replace an expired credential through network account-updater services where the customer’s issuer participates. This does not authorise an Order without the customer’s purchase instruction.
11. Fraud prevention and risk review
11.1 Snap Matrix and the Payment Provider assess signals such as payment result, authentication, velocity, device, network, billing consistency, Account history, compromised-card indicators and unusual Token usage to prevent fraud and abuse.
11.2 A payment may be declined, held, cancelled or refunded where there is a reasonable security or compliance concern. A review is not an allegation of wrongdoing and may be resolved by proportionate additional verification.
11.3 Verification may request confirmation of Account control, billing details or a limited proof of payment ownership. Snap Matrix will not request a complete unmasked card, card security code or online-banking password.
11.4 Automated risk tools support decisions but do not remove applicable rights concerning significant solely automated decisions. The Privacy Policy explains review and objection routes.
12. Failed, interrupted and duplicate attempts
12.1 A decline can result from issuer limits, insufficient funds, authentication failure, unsupported method, mismatched details, geographic restrictions, provider outage or risk controls. The issuer often has the most specific reason.
12.2 The customer should not repeatedly resubmit while a transaction remains pending. Repeated attempts can create multiple authorisation holds or separate successful Orders.
12.3 If the browser closes after payment, the customer should check the Account and email confirmation before paying again. Snap Matrix reconciles provider callbacks and can attach a successful payment to the correct Order.
12.4 A verified duplicate capture for one intended Order is refundable under the Refund Policy. Two separately confirmed Token Packs are not duplicates merely because they have the same amount and occur close together.
13. Payment troubleshooting table
13.1 Use the least intrusive route that matches the observed state.
| Observed issue | First action | Do not do | Escalation evidence |
| Declined immediately | Verify details and contact issuer | Do not email full card data | Order attempt time and issuer message |
| Authentication loop | Return through issuer page or try supported browser | Do not share one-time code | Screenshot without credentials |
| Pending bank entry, no Order | Wait for final status and contact support | Do not assume capture | Amount, date, masked card digits |
| Paid, no Tokens | Refresh Account and report Order reference | Do not purchase again immediately | Receipt and Account email |
| Two settled entries | Compare Order IDs and report both | Do not dispute both automatically | Statement dates and receipts |
| Refund not visible | Allow issuer posting period, then query issuer | Do not send new card details | Refund reference and initiation date |
14. Delivery after payment
14.1 A Token Pack is fulfilled when the stated quantity is credited to the Account. Paid photo content is fulfilled when it becomes available to view or download. A paid generation is fulfilled when the completed Output becomes available as described in the Digital Product Fulfilment Policy.
14.2 The payment confirmation and fulfilment event are linked but distinct. A successful charge with failed fulfilment is corrected through supply, Token restoration or refund; a failed authorisation does not create a delivery obligation.
14.3 A security review may delay crediting for up to twenty-four hours. Where Snap Matrix cannot resolve the payment or safely fulfil, it will void or refund the transaction rather than leave an indefinite pending Order.
14.4 The customer is responsible for maintaining access to the Account email and checking spam or filtered folders. Account-based delivery remains available independently of email delivery where technically possible.
15. Tokens and financial-character restrictions
15.1 Tokens represent a limited right to request specified Snap Matrix services. They are issued by Trexadoc OÜ for closed-loop use and do not constitute funds held for the customer.
15.2 Tokens cannot be withdrawn to a bank account, exchanged for fiat or cryptoassets, transferred between users, pledged, sold, traded or used to pay another merchant. Snap Matrix does not promise appreciation, yield, liquidity or redemption value.
15.3 The Token price may change for future Orders. A price change does not increase or decrease the quantity already credited, create a mark-to-market claim or entitle the customer to the difference.
15.4 A correction, refund or chargeback may reverse Tokens linked to the affected payment. Promotional Tokens may be distinguished from paid Tokens in the ledger and may expire under clearly stated campaign terms.
16. Refunds, reversals and credits
16.1 Refund eligibility is governed by the Refund Policy and mandatory law. Approved refunds ordinarily return to the original payment method and are initiated without undue delay within any statutory maximum.
16.2 Issuer posting commonly takes five to ten business days after initiation. Snap Matrix can provide a provider reference but cannot force the issuer to post on a particular date.
16.3 A refund may be accompanied by removal of unused Tokens, paid-content access or other benefits from the Order. A failed generation may instead result in Token restoration without reversing the whole purchase.
16.4 Store credit is offered only as an optional lawful alternative and does not replace a monetary refund where the customer is entitled to money and has not agreed to credit.
17. Chargebacks and card-scheme processes
17.1 Cardholders retain rights to contact their issuer. Snap Matrix encourages direct contact for fulfilment or billing errors because the merchant can often resolve them without the delay and restrictions of a chargeback.
17.2 Upon notice of a dispute, Snap Matrix may submit accurate evidence through the Payment Provider, including the Order, authentication result, product description, immediate-supply consent, Token credit and use, download or generation records, and support history.
17.3 The related Account entitlement may be suspended while the payment is reversed or disputed so that the same benefit is not retained without payment. Suspension is adjusted if the issuer resolves the dispute in the customer’s favour or the amount is repaid.
17.4 Knowingly false disputes, collusion or repeated purchase-use-chargeback conduct may lead to Account termination and reporting to relevant providers or authorities, without affecting legitimate consumer or card-scheme rights.
18. Taxes, invoices and business customers
18.1 Snap Matrix issues transaction documentation in the form required for the sale. A customer requesting a business invoice must provide accurate legal name, address and valid tax information before or promptly after purchase where the system permits correction.
18.2 A value-added tax number may be validated and retained with evidence of the customer’s location and status. Submission does not guarantee zero-rating or reverse charge; the applicable tax rule controls.
18.3 A consumer must not misstate business status to avoid tax or consumer-facing controls. A business customer must ensure that the person placing the Order has authority to bind it.
18.4 Accounting records and source documents are retained for the statutory period, ordinarily seven years under Estonian accounting requirements, even if the Account is later closed.
19. Sanctions, restricted transactions and legal compliance
19.1 Snap Matrix may refuse or block a payment where required by sanctions, anti-money-laundering measures applicable to the provider, card-network rules, court order, fraud controls or restrictions on the underlying content.
19.2 The Service may not be used to route payments, cash out value, test stolen cards, disguise the beneficiary, evade geographic controls or purchase generation services for unlawful conduct.
19.3 A compliance hold is limited to what is reasonably necessary. Where funds were captured but Snap Matrix cannot lawfully fulfil, the amount will be handled according to applicable law and provider requirements rather than converted to Tokens.
19.4 Snap Matrix may request information necessary to distinguish a false positive, but it is not required to disclose confidential detection rules or information whose disclosure is legally prohibited.
20. Customer responsibilities
20.1 The customer must provide accurate checkout information, use an authorised payment method, review the amount and product, complete issuer authentication, and keep the Order confirmation.
20.2 The customer must promptly report an unknown Order, duplicate charge, missing entitlement or incorrect Token balance. Delay may make technical investigation harder but does not remove non-waivable rights.
20.3 The customer must not share Account credentials, permit an unauthorised person to use a saved method, manipulate checkout requests, exploit pricing errors or circumvent purchase limits.
20.4 A parent or other person whose payment method was used by an underage user should secure the method and contact the issuer and Snap Matrix. The Service is restricted to users aged eighteen or older.
21. Payment records and privacy
21.1 Snap Matrix processes Order details, masked payment data, provider tokens, authentication and risk results, billing information, tax evidence, refunds and disputes for contract performance, legal obligations and legitimate fraud-prevention interests.
21.2 The Payment Provider separately processes cardholder data under its notice and regulatory responsibilities. Snap Matrix does not control every network, issuer or authentication use of that data.
21.3 Transaction and accounting records are retained as required by law. Fraud and dispute evidence may be retained for applicable network and legal-defence periods. The Privacy Policy explains rights, recipients, transfers and complaint routes.
21.4 Support staff access payment records on a role-based basis. Full card security data should never be placed in prompts, uploaded images, ordinary email or support tickets.
22. Service changes and payment-provider substitution
22.1 Snap Matrix may change the Payment Provider, accepted methods, checkout design or fraud controls. A substitution must preserve accurate price disclosure, secure processing, receipts, refunds and mandatory customer rights.
22.2 A method can be withdrawn for future Orders without cancelling a completed Order. An existing refund will still be sent through the original route where practicable or another lawful agreed route.
22.3 Material changes to payment practices are reflected in this Policy before they apply to future purchases. No update creates recurring authority for an existing customer.
22.4 Technical maintenance may temporarily disable checkout. Snap Matrix is not required to accept an Order during an outage or risk event, but it remains responsible for reconciling any payment that was actually captured.
23. Complaints and dispute route
23.1 Payment questions should be sent to info@snap-matrix.com with the Account email, Order ID, amount, date and a concise description. Use only masked card information, normally the scheme and last four digits.
23.2 Snap Matrix aims to acknowledge a complete complaint within two business days and issue a reasoned outcome within ten business days, subject to complexity and mandatory deadlines.
23.3 A consumer may use the complaint and external-resolution route stated in the Terms and Refund Policy, including the competent Estonian consumer-dispute body. Cardholder rights with the issuer remain separate.
23.4 The discontinued European Union Online Dispute Resolution platform is not described as an active channel. Court rights and mandatory jurisdiction rules are unaffected.
24. Practical purchase and payment checklist
24.1 Before purchase: confirm the correct Account, Token quantity or content, final price, currency, tax, system requirements and immediate-supply terms.
24.2 At payment: use an authorised method, complete the issuer challenge only in the secure interface, and do not refresh or resubmit repeatedly while the result is pending.
24.3 After payment: retain the Order confirmation, verify the Token balance or content entitlement, and report any mismatch before using a duplicate purchase.
24.4 For support: provide the Order ID, date, amount and masked method. Never send a password, one-time authentication code, complete card number or card verification code.
Operational payment path
| Step | Action |
| 1. Review | Confirm product, quantity, price, currency, tax and digital-supply consent. |
| 2. Authorise | Select the payment method and complete any issuer authentication. |
| 3. Confirm | Wait for the checkout result and retain the Order confirmation. |
| 4. Verify fulfilment | Check the Account ledger, purchased content or generated Output. |
| 5. Resolve anomalies | Contact support before paying again if the bank shows a pending or settled entry but no Order appears. |
| 6. Preserve security | Use masked details only and contact the issuer immediately for suspected unauthorised use. |
25. Contact
25.1 Payment, invoice, descriptor and transaction questions may be sent to info@snap-matrix.com. State “Payment query – Order [ID]” where an Order exists.
25.2 Trexadoc OÜ can investigate merchant records but cannot disclose an issuer’s confidential decline rule or access the customer’s banking account. The issuer should be contacted for account-specific holds, limits and posting.
25.3 Formal notices may also be sent to the registered office shown in the Operator table. Email is the fastest operational route and should not contain complete card credentials.
Snap Matrix · Payment Policy · v1.0 · effective 29 July 2026. This version applies from the effective date and supersedes earlier versions for future use.