Reporting & data
Read store orders and payment totals
Use provider-verified payment state and keep live payments, test payments and service fulfillment separate.
Distinguish the three kinds of status
An order records the selected discovery service and agreed price. Payment status reflects a verified provider response or signed event. Fulfillment status describes the team’s work on the service. One status should not be used as proof of another.
- Check whether the order is test or live.
- Check its payment state and verification information.
- Review the fulfillment stage and notes separately.
- Test payments are excluded from live paid totals.
- Gross verified order payments are not a statement of recognized revenue.
Compare reports using the stated period
Management reports may group orders by when they were created. A payment can settle in a different period. Read the report basis before comparing it with a provider payout, accounting report or sales pipeline.
- Use the same currency, date basis and environment.
- Check the order’s saved service and price snapshot.
- Treat refunds, disputes, fees and settlement questions as separate provider or accounting evidence.
If a paid order is unclear
Use the order reference and contact the team before paying again. A success URL alone does not establish that the application has verified and recorded a payment.
- The order reference through a private channel.
- The approximate payment time and selected service.
- The visible payment state, without card details or private checkout links.
Need help with your workspace?
Open a private support request with the steps, expected result and business impact. Leave out passwords, API keys and payment details.
Open client support