# BuyerProtection.com.au

> Public store proof before payment. Private order context after payment.

## Exact use moments

- Before checkout: check who operates the store, which domain is proven and where support starts.
- When a cardholder does not recognise a payment: open the merchant, statement name, amount and order together.
- When delivery or a refund is questioned: show source-linked events and one exact next step.
- When a new merchant needs a path into payment acceptance: refer a merchant-owned proof workflow without turning signup into approval.
- When an existing merchant is under dispute pressure: refer a measured remediation workflow before more buyer issues escalate into formal chargebacks.
- When a bank sees an unfamiliar payee or store: compare the official domain, verified payment identity and observed commerce evidence without outsourcing the bank's decision.
- When an AI agent considers a merchant: query the public status, but never treat Verified as Guaranteed or Unknown as fraudulent.

## Public labels

- Unknown: no public BuyerProtection proof record was found. This is not a scam verdict.
- TrustedSite Verified: a live public business and domain proof record exists. Order backing appears only under a separate live Guaranteed result.
- BuyerProtection Guaranteed: a separately active status that still requires the order scope, current terms and an order-specific decision to agree.

## Public machine surfaces

- Store check: https://buyerprotection.com.au/api/v1/merchant-trust?domain=trustedsite.com.au
- Agent manifest: https://buyerprotection.com.au/.well-known/buyerprotection/agent.json
- Procurement facts: https://buyerprotection.com.au/.well-known/buyerprotection/procurement.json
- Service-provider register: https://buyerprotection.com.au/.well-known/buyerprotection/service-providers.json
- Data lifecycle register: https://buyerprotection.com.au/.well-known/buyerprotection/data-lifecycle.json
- Partner distribution contract: https://buyerprotection.com.au/.well-known/buyerprotection/partner-distribution.json
- Merchant Assurance contract: https://buyerprotection.com.au/.well-known/buyerprotection/merchant-assurance.json
- OpenAPI: https://buyerprotection.com.au/openapi.json
- Public readiness: https://buyerprotection.com.au/api/v1/public-readiness
- Trust Centre: https://buyerprotection.com.au/trust-centre
- Example private order: https://buyerprotection.com.au/order-passport/example
- Example evidence packet: https://buyerprotection.com.au/api/v1/evidence-packets/example

## Available now

- Live public store checks with source, status and validity.
- Signed, expiring Order Passport examples for private post-purchase context.
- Versioned API, schema, procurement, security, data and readiness records.
- Controlled Shopify evidence connections for authorised merchants.
- Product reviews for banks and platforms using one de-identified transaction workflow.

## How trust is earned

- A merchant account opens the workspace. TrustedSite Verified follows authorised business, domain and support review.
- A partner referral introduces the merchant. The merchant keeps the account and explicitly chooses any aggregate milestone sharing.
- BuyerProtection Guaranteed appears only on an eligible live result after evidence, capacity and a recorded human decision agree.
- Partner outcome claims are published only after the defined cohort is independently reconciled against its agreed baseline.

Enterprise production access follows the counterparty's security, data, authority, contract and release approvals. The machine-readable readiness and procurement records carry the exact current state for those reviews.

## Integration boundary

BuyerProtection adds merchant and order context beside existing authorisation, acquiring, fraud, support and dispute systems. It does not replace a bank, payment processor, card scheme, marketplace, Australian Consumer Law right or regulated decision.