TRUST CENTER
Clear boundaries for checkout, data and operational responsibility.
This public Trust Center states what HustlePay can support without claiming certifications, audits or regulatory status that have not been published and verified.
Who does what
| Party | Public responsibility |
|---|---|
| HustlePay | Checkout-session creation, orchestration instructions, status exchange and connected product experience. |
| Merchant | Products, prices, customer relationship, PSP accounts, permissions, refunds, disputes and store compliance. |
| PSPs | Method eligibility, authorization, processing, settlement and provider controls. |
Data and implementation controls
The WooCommerce connector can use order, item, amount, currency, tax, shipping, return/callback and customer billing/contact context. It does not store full card numbers or CVVs. Merchants should protect credentials, limit access, use matching test environments, validate signed callbacks and document incident ownership.
Trust and security questions
Does HustlePay hold merchant funds?
No public custodial or settlement claim is made. PSPs remain responsible for processing and settlement. Published claims remain limited to documented controls and responsibilities; account-specific evidence can be requested through the appropriate support or diligence route.
Does HustlePay replace my payment service provider?
No. HustlePay coordinates the connected checkout flow; the merchant keeps its PSP accounts, agreements and provider responsibilities. Published claims remain limited to documented controls and responsibilities; account-specific evidence can be requested through the appropriate support or diligence route.
Does the site claim a security certification?
No unpublished certification, audit or regulatory status is claimed. Published claims remain limited to documented controls and responsibilities; account-specific evidence can be requested through the appropriate support or diligence route.
Does HustlePay store card details?
The public WooCommerce connector says it does not store full card numbers or CVVs. Payment-method collection remains within the connected checkout and PSP flow. Published claims remain limited to documented controls and responsibilities; account-specific evidence can be requested through the appropriate support or diligence route.
Who handles fraud checks and authorization?
The relevant PSP applies its authorization, fraud and provider controls. HustlePay does not claim to replace those PSP decisions. Published claims remain limited to documented controls and responsibilities; account-specific evidence can be requested through the appropriate support or diligence route.
Where are payment details entered?
Payment-method collection occurs within the connected checkout and PSP flow; never send credentials through normal forms. Published claims remain limited to documented controls and responsibilities; account-specific evidence can be requested through the appropriate support or diligence route.
How should an incident be reported?
Use the support route with environment, timestamp, safe identifiers and impact, without sending passwords or full payment credentials. Published claims remain limited to documented controls and responsibilities; account-specific evidence can be requested through the appropriate support or diligence route.
Need implementation or security information?
Tell us the product, environment and question. Do not send passwords, API secrets, full card details or CVVs.