Anti-fraud policy

This site is operated independently by me (0x00 on Discord). Card payments go through Stripe and cryptocurrency payments through a third-party crypto payment processor. Both providers run industry-standard fraud controls that decide whether a charge is approved at all. Once a payment is approved, an automated system credits coins to the PGTools username immediately. My role is to set the risk rules, monitor for patterns the processors can miss, and act decisively when fraud is confirmed after delivery.

Each card transaction is scored in real time by Stripe Radar before the charge is captured. The signals that feed the score include:

• Stripe Radar risk scoring for known card-fraud patterns.
• 3D Secure (3DS) step-up authentication on elevated-risk or high-value charges.
• IP address geolocation and VPN / proxy detection.
• Velocity checks on repeated attempts from the same card, IP, or username.

On top of the processor's signals, I maintain a private blocklist of cards, IPs, and usernames tied to prior chargebacks or abuse cases. Charges that match the blocklist are refused before any processor is even asked to authorize them.

The following are grounds for immediate order cancellation and permanent ban:

• Paying with a card, account, or wallet you do not own or are not authorized to use.
• Creating multiple accounts to abuse promotions, referral credits, or trial features.
• Submitting false or misleading information on payment or support requests.
• Attempting to circumvent fraud controls, including proxy chaining, card cycling, and identity spoofing.
• Money laundering, sanctions evasion, or any activity prohibited under EU or local law.

The processor, not me, decides whether a charge is captured. Coins are delivered only once a charge has captured cleanly:

• Declined · Stripe may refuse the charge outright when Radar scores it too risky. The card is not charged and no coins move.
• Challenged with 3DS · elevated-risk charges are stepped up to 3D Secure. Passing 3DS captures the charge and triggers credit; failing it cancels the charge.
• Crypto confirmations · crypto invoices only credit once the network confirms the required number of blocks. Expired invoices never credit; underpaid invoices are held for manual review and only credited if I confirm the payment and process it myself.
• Blocklisted identifiers · charges matching the private blocklist described in Section 02 are refused before the processor is contacted.

For card payments there is no manual-hold queue between payment and delivery: a captured payment credits coins immediately through the automated system; a declined payment never reaches that step. Underpaid crypto invoices are the one exception — they pause until I review and either accept or refund the partial payment. Anything else I need to check happens after delivery, in the next section.

Delivery does not end the review. I periodically examine order patterns across identifiers (card, IP, username) for signals that pre-capture checks can miss. For example, a single card funding several unrelated PGTools usernames within hours, or a username cluster that correlates with a prior chargeback. Reviews are triggered by thresholds or by reports from buyers; there is no blanket surveillance of individual orders.

Chargebacks that bypass direct support are treated the same way. I contest them with the full evidence set described in the refund policy.

If you believe someone has used your payment method to buy PGTools coins on this site without your consent, message me on Discord or email [email protected] immediately. Include:

• The transaction date and approximate amount.
• The last four digits of the card or the crypto transaction hash.
• A brief description of how you became aware of the charge.

I will freeze further use of the credited coins, flag the associated identifiers, and coordinate with the relevant payment processor on the refund. Response times are listed on the support page.