Payment Policy

Skins Dealer · Payment Policy · v1.0 · Effective 29 July 2026

FieldValue
OperatorPebletex OÜ
Company number17367621
Registered officeTelliskivi tn 60a/5, Põhja-Tallinna linnaosa, 10412 Tallinn, Harju maakond, Estonia
Trading name / brandSkins Dealer
Websitehttps://skins-dealer.com
Contact emailinfo@skins-dealer.com
Support / complaintsinfo@skins-dealer.com; Monday to Friday, 09:00-17:00 Eastern European Time / Eastern European Summer Time, excluding public holidays in Estonia
Governing lawLaws of Estonia, subject to mandatory consumer protections
Document versionv1.0
Effective date29 July 2026
Important: Payments buy identified digital skins for delivery to a supported account. Prices and taxes are shown before submission, the expected statement descriptor is SKINS-DEALER, and approved refunds are returned to the original payment method. Skins Dealer does not operate a deposit wallet or cash-out service.

1. Scope and purpose

This Payment Policy explains how Orders are priced, authorised, verified, captured, recorded, declined, reversed, refunded and disputed. It applies to card and other methods shown at checkout.

The policy should be read with the Terms and Conditions, Refund Policy and Digital Product Fulfilment Policy.

2. Nature of transactions

Each payment is consideration for a specific Digital Item or entitlement described before checkout. The transaction is a retail purchase, not a deposit, remittance, investment, wager or purchase of electronic money.

No recurring billing or automatic subscription is created unless a future product page expressly states otherwise and obtains separate consent.

3. Accepted payment methods

Eligible Visa and Mastercard cards may be accepted, together with other methods displayed at checkout. Availability depends on country, currency, Payment Provider, issuer and risk controls.

A logo or method shown on a general page does not guarantee approval for every Order. The checkout confirmation is the controlling availability signal.

4. Billing currencies and pricing display

Prices are normally displayed and charged in EUR. If another currency is supported, the checkout identifies the billing currency before payment.

The final payable amount is shown before submission. You must review item, quantity, platform, account destination, currency and total. External market prices do not determine the contractual price after acceptance.

5. Taxes and charges

Displayed consumer prices include value-added tax or other taxes where the law requires inclusion. Any separately calculated charge is shown before payment.

Your issuer may impose foreign-exchange, cross-border or card fees. Those charges are not collected by Pebletex OÜ and are not refunded by us unless law requires.

6. Authorisation and transaction completion

Submitting payment authorises the Payment Provider and issuer to verify and, if approved, reserve or capture the amount. An authorisation may remain pending before settlement and can be released without becoming a completed charge.

An Order is accepted when we issue confirmation after successful payment and risk checks. Payment completion and Digital Item fulfilment are related but distinct events.

7. Use of third-party payment providers

Payment processing is performed by an independent Payment Provider identified in the checkout or transaction record. The provider may use card networks, acquiring banks, issuers, identity services and fraud tools.

Full card data is entered into the provider’s secured environment and is not intended to be stored by Pebletex OÜ. We receive transaction identifiers, status, masked details and risk results needed for operations.

8. Security, verification and fraud controls

Checkout may use transport encryption, tokenisation, Payment Card Industry Data Security Standard-aligned provider controls, strong customer authentication and three-domain secure verification.

We may request additional evidence where account, device, payment and destination details create unusual risk. Verification is designed to prevent stolen-card use, sanctions evasion, duplicate claims and unauthorised delivery.

9. User payment responsibilities

Use only a payment method you are authorised to use and provide accurate billing information. Ensure sufficient funds and complete issuer authentication personally.

Do not split transactions to avoid limits, route payments through unrelated persons, use anonymising techniques to conceal prohibited geography or resubmit a pending transaction repeatedly.

10. Declined, failed or reversed payments

An issuer or Payment Provider may decline a transaction for insufficient funds, authentication failure, risk rules, geographic restrictions or technical reasons. We may not receive the specific reason.

A failed or reversed payment does not create a right to delivery. A temporary authorisation normally disappears according to issuer timing. Contact the issuer if a released authorisation remains visible beyond its normal period.

11. Duplicate charges and technical errors

If the same intended purchase appears twice as completed, contact support before using or transferring any duplicated item. We will compare transaction identifiers, timestamps and fulfilment records.

A pending authorisation beside a settled charge is not necessarily a duplicate. Genuine duplicate capture is corrected or refunded to the original method.

12. Unauthorised transactions and security reporting

Report unauthorised use immediately to the issuer and to us. Secure the Account, email and Supported Platform credentials and preserve relevant alerts.

We may suspend uncompleted delivery, restrict the Account and share evidence with the Payment Provider, issuer or authorities. A good-faith report does not prejudice statutory or scheme rights.

13. Refunds and relationship to the Refund Policy

Eligibility, evidence, timeframes and entitlement consequences are set out in the Refund Policy. Approved refunds are normally returned to the original payment method and currency.

A refund does not become a transferable cash balance. The related Digital Item may be reversed, disabled or reclaimed, and continued use after reimbursement is prohibited.

14. Chargebacks, retrievals and disputes

Contact support first where a delivery or duplicate issue can be resolved directly. This is a practical request, not a waiver of cardholder rights.

A retrieval or chargeback may require us to provide the acquirer with order, authentication, descriptor, communication and fulfilment evidence. Direct refund handling may pause to prevent double reimbursement.

15. Timing of delivery and account crediting

Delivery normally occurs normally within minutes and no later than 24 hours after successful payment and any required verification after payment is successful and verification is complete.

High-risk review, destination restrictions, platform maintenance or a required transfer acceptance may extend the time. The Fulfilment Policy explains completion and evidence.

16. Payment records and audit trail

We retain transaction reference, amount, currency, status, masked instrument information, authentication result, order details, delivery evidence and support history.

Records support accounting, tax, fraud prevention, refunds and dispute response and are retained under the Privacy Policy.

17. Geographic and legal restrictions

Payments may be unavailable in sanctioned, prohibited or unsupported jurisdictions. We may reject transactions involving restricted persons, unlawful goods, money laundering indicators or payment methods not permitted by the provider.

You must not use the Service to move value, cash out virtual items, finance gambling or disguise the origin or destination of funds.

18. Minors and payment authority

Customers must be at least 18 years old. A person must not use a parent’s, employer’s or other third party’s payment method without clear authority.

We may request proof of age, identity or payment authority and may cancel or refund a transaction where lawful control cannot be established.

19. Changes to prices, methods and rules

Catalogue prices and available methods may change before an Order is accepted. A confirmed Order is not repriced because an external market later changes.

Obvious pricing errors may lead to cancellation before fulfilment. Any captured amount is returned promptly to the original method.

20. Service interruptions and processor downtime

Payment functionality may be unavailable during provider outages, maintenance or security incidents. Do not repeatedly submit payment during an uncertain status.

We reconcile interrupted transactions and either continue a valid Order, release or refund the amount, or request a fresh payment after confirming that no duplicate capture occurred.

21. Contact and complaint route

Payment questions should be sent to info@skins-dealer.com with the Order reference, date, amount and last four digits only where needed. Never send the full card number or security code.

We aim to acknowledge complaints within two business days and provide an outcome or progress update within ten business days.

22. Updates

This policy may be revised for legal, card-scheme, security or provider changes. The version and effective date identify the current rules.

The payment terms accepted for an Order remain available in transaction records, subject to mandatory law.

Payment lifecycle

StageWhat normally happensTypical statusKey risk / control
1. CheckoutItem, account, EUR price, tax and method are displayedReady for submissionCustomer review; no hidden recurring charge
2. AuthenticationProvider and issuer verify the cardholderChallenge, frictionless or declinedStrong customer authentication / three-domain secure
3. AuthorisationIssuer reserves or approves the amountPending or authorisedDo not repeat while status is uncertain
4. Risk reviewAccount, device, payment and destination signals are assessedApproved, manual review or rejectedFraud and sanctions controls
5. CaptureApproved payment is settled or prepared for settlementCaptured / completedTransaction identifier and descriptor recorded
6. FulfilmentDigital Item is credited, transferred or activatedDelivered, pending or failedPlatform logs and destination confirmation
7. AftercareSupport, refund or dispute handled if neededClosed, refunded or disputedOriginal-method refund and evidence preservation

Practical payment lifecycle overview

P.1 Select the exact Digital Item and verify the Supported Platform and destination account before opening checkout.

P.2 Review the final EUR total, taxes, merchant identity and expected descriptor before submitting payment.

P.3 Complete issuer authentication once and wait for a clear result; do not retry a pending transaction.

P.4 Monitor the Order page and email for verification or transfer actions required to complete delivery.

P.5 Report a duplicate, unauthorised or incorrect charge promptly with the Order reference and masked evidence.

P.6 Preserve the delivered item while a refund or card dispute is reviewed so that a lawful remedy can be completed.

Good practice for users before submitting payment

  • Use a payment method in your own name or one you are expressly authorised to use.
  • Confirm that the destination platform account is active, secure and able to receive transfers.
  • Check currency and issuer foreign-exchange costs before authorising the transaction.
  • Keep the Order confirmation and recognise the statement descriptor SKINS-DEALER.
  • Contact support instead of making repeated payment attempts when a status is unclear.

Schedule 1. Payment Control Standards

These controls explain how payment events are authenticated, reconciled, investigated and communicated across the checkout lifecycle.

Merchant identification and descriptor recognition

The contracting merchant is Pebletex OÜ trading as Skins Dealer. Checkout, confirmation and support communications should enable the payer to identify the merchant, the item purchased, the amount and the statement descriptor SKINS-DEALER. The user should contact support promptly if the descriptor is not recognised. Clear descriptor recognition reduces avoidable disputes but does not limit the payer’s right to report a genuinely unauthorised transaction to the issuer.

Authentication allocation

A card issuer, acquirer or payment provider may require Strong Customer Authentication, an issuer challenge, device confirmation or another verification step. Skins Dealer cannot bypass an issuer decision or guarantee that a challenge will be available. The user must complete authentication through the official issuer or payment-provider channel and must never disclose a one-time code to support. An abandoned or failed challenge can leave an authorisation pending without creating a completed Order.

Authorisation, capture and settlement

Authorisation reserves or confirms funds; capture records the merchant’s request for payment; settlement transfers value through the acquiring chain. These stages may occur at different times. A pending authorisation can disappear without a charge, while a captured transaction can later be reversed or refunded. The Order status shown by Skins Dealer is the service record, but the payer’s bank statement remains controlled by the issuer and may use its own posting dates and currency labels.

Risk-based manual review

A transaction may be held before delivery when indicators suggest stolen credentials, account takeover, location inconsistency, excessive velocity, repeated declines, abnormal device behaviour or a mismatch between payer and destination. Review is proportionate and does not guarantee that fraud will be detected. Skins Dealer may request limited identity or payment-authority evidence, cancel the transaction, release the hold or proceed with delivery. Complete card numbers and card security codes must not be submitted.

Reconciliation and exception handling

Skins Dealer reconciles Orders against payment-provider reports to identify a successful payment without an Order, an Order without settled payment, a duplicated capture, an unmatched refund or a processor reversal. Exceptions are investigated using the Order identifier, provider reference, amount, currency and timestamp. Reconciliation corrections do not create a right to receive an item without valid payment, and a user must not exploit an obvious duplicate credit or delivery.

Currency conversion and issuer charges

Prices are stated in euros unless checkout expressly states another currency. A card issuer or payment service may convert the amount, add a cross-border fee or apply its own exchange rate. Those charges are outside the amount collected by Skins Dealer and should be reviewed with the issuer. Skins Dealer does not add a hidden conversion margin after authorisation and will show the merchant charge currency before the user confirms payment.

Evidence for payment complaints

A useful payment complaint includes the Order number, charged amount, currency, date, last four digits or payment-method reference, screenshot of the relevant statement entry and a description of the expected outcome. Passwords, full card numbers, card security codes and one-time authentication codes must be omitted. Skins Dealer may provide an authorisation, capture, refund or acquirer reference when available, but cannot disclose another person’s account or payment information.

Processor continuity and fallback

If a processor or card network is unavailable, checkout may be suspended, a different displayed method may be offered or an incomplete attempt may be allowed to expire. Skins Dealer will not ask a user to send card credentials by email or chat as a workaround. A fallback method is used only when it is visibly offered through the secure checkout and the price, merchant identity and Order terms remain clear before authorisation.

Skins Dealer · Payment Policy · v1.0 · Effective 29 July 2026. The version made available through the Website is the controlling customer-facing version.