Trust Center • Onboarding • Verification • Security Logging
Onboarding & Verification Policy
Merchants hate “KYC loops”. This page explains our onboarding approach, what we log for security, and who is responsible for refunds/disputes — in plain English.
Fast start for standard merchants. Risk-based escalation only if needed.
WAF + rate limits + service logs to protect platform stability.
Refunds & disputes depend on payment method rules and merchant policies.
1) Onboarding (No KYC loops)
We are high-risk friendly — but not “anything goes”. We support legal businesses and focus on fast onboarding without the document ping-pong that wastes weeks.
Our position: We avoid invasive document onboarding for standard merchants. We use risk-based onboarding and may request enhanced verification only if volume, dispute patterns, or risk indicators require it.
- Standard onboarding does not require invasive identity-document back-and-forth.
- You can integrate quickly (WooCommerce, links, products/landing pages, API).
- Clear rules: legal businesses only, comply with terms and acceptable use.
- Unusual volume spikes or elevated dispute/chargeback patterns
- Risk indicators (abuse signals, compromised traffic, policy violations)
- Payment-method/provider requirements for specific flows
This is exactly how serious payment infrastructure behaves: fast standard onboarding, targeted escalation only when required.
2) Customer verification
We do not run a consumer identity program and we do not ask your customers to upload IDs to EcomTrade24 Pay as a standard step.
- Some payment methods/providers may apply their own verification rules on certain transactions.
- This is not “merchant KYC onboarding” — it is payment-network/provider risk control on specific payments.
- We aim to route payments in a way that reduces friction where possible.
3) Security logging & abuse prevention
Merchants confuse “transaction surveillance” with basic security operations. We do not build advertising profiles — but we do protect the platform.
- Abuse prevention (rate limiting, bot protection, WAF/security events)
- Service reliability logs (errors, uptime, incident diagnostics)
- Session-level metadata required to operate payments (references, timestamps)
- We don’t sell personal data or build advertising profiles.
- We don’t run “spyware-style” tracking across the internet.
- We don’t ask customers to upload identity documents to EcomTrade24 Pay as a standard step.
Payment methods/providers may still apply their own risk/compliance checks depending on the method and jurisdiction.
Plain truth: We do operate security logging and abuse prevention to protect the platform (for example: WAF events, rate limiting, error logs, and suspicious traffic signals). We do not sell personal data or build advertising profiles.
4) Refunds, disputes & chargebacks
Refunds, disputes, and chargebacks are handled by the merchant and/or the underlying payment provider/network, depending on the payment method.
- Publish a clear refund/returns policy on your website.
- Support requests should be handled by the merchant first.
- Dispute outcomes and timelines depend on payment method rules and provider processes.
5) Minimal data & retention
We aim for data minimization. We store what is required to operate the platform securely and to support merchants. We do not store identity documents as part of standard operations.
- Service logs (errors, uptime events, abuse prevention)
- Request metadata (timestamp, endpoint, basic security signals)
- Merchant configuration (domains, webhook URLs) provided by merchants
For details, see our Privacy Policy.
6) Contact
Questions about onboarding, verification, or security? Contact us at [email protected] or use the support form.
FAQ
Is there KYC/KYB to start?
We avoid invasive document onboarding for standard merchants. We use risk-based onboarding and may request enhanced verification only if volume, dispute patterns, or risk indicators require it.
Do you ever ask customers for ID?
We do not run a consumer identity program and we do not ask your customers to upload IDs to EcomTrade24 Pay as a standard step. In rare cases, a payment method/provider may request verification as part of their own rules.
Do you “monitor transactions”?
We do not run a marketing-style surveillance system. We do maintain security logs and risk signals to prevent abuse and keep the platform stable. Payment methods/providers may apply their own compliance/risk checks.
Who handles refunds and disputes?
Refunds, disputes, and chargebacks are handled by the merchant and/or the underlying payment provider/network, depending on the payment method.
Are you high-risk friendly?
Yes — we support complex industries that get blocked elsewhere, as long as the business is legal and complies with our acceptable use and terms.