By the VIXI team · Reviewed
Where to start
Confirm that two records represent the same business transaction before calling them duplicates. Then trace every system that can send that sale to HYROS. Checkout and processor overlap, workflow retries and multiple events for one payment need different fixes.
Different symptoms require different checks
| What you see | What to investigate | Evidence to compare |
|---|---|---|
| Two HYROS sales for one paid order | Overlapping checkout, processor or custom integrations. | Source transaction, amount, time and delivery path for both records. |
| Extra records after a failed workflow is retried | Whether the first request succeeded before the retry. | Workflow execution, response and the existing destination sale. |
| Invoice and payment events both create a sale | Whether two event types describe the same payment. | The business transaction and the mapping for each event type. |
| The same customer buys again | A legitimate renewal, installment or separate order. | Distinct transaction IDs and the agreed subscription rules. |
1. Confirm the duplication with one transaction
Start with one paid order and find the records that appear to duplicate it. Match the source transaction and its relationship to each destination record. An identical email, similar time or repeated amount is a clue, not enough proof by itself.
A renewal or installment can belong to the same customer and still be a legitimate new sale. Record those cases separately so the repair does not suppress future revenue. Keep identifiers and screenshots in the private audit record.
2. Map all systems that send the sale
List the checkout connection, payment-processor connection, custom API workflows, manual imports and any other sender in the actual setup. For each, document its trigger, business event, destination and owner.
HYROS’s Stripe installation guidance warns that connecting both a checkout and its processor can create duplicate sales. Check whether both paths are sending this same payment before changing either connection.
Choose the intended source with the team responsible for the setup. Check which products and payment methods it covers. Removing a connection without that inventory can stop valid events that only travel through that connection.
Reference: HYROS: Stripe integration and overlapping payment sources ↗
3. Check webhook and n8n retry behavior
Stripe documents that webhook events can arrive more than once. It recommends tracking processed event IDs; for separate events describing the same object and event type, compare those fields as well. This concerns webhook handling and is not a guarantee that every HYROS integration uses the same deduplication rules.
For a custom workflow, document how one business transaction maps to one intended sale. A delivery ID identifies a message; an order or payment ID identifies a business object. Choose the deduplication rule around the sale definition and preserve legitimate recurring payments.
A timeout does not prove that HYROS rejected the request. Inspect the destination before replaying the workflow. For custom code, use the destination’s documented retry behavior and a durable processing record where needed; do not rely on a person remembering which executions were rerun.
Reference: Stripe: handling duplicate webhook events ↗
4. Verify the repair and review historical records separately
Define the test and a rollback plan before editing the live integration. Use the supported test environment where available, or an explicitly authorized transaction. Record which configuration changed and when.
Stopping the extra sender does not establish that older duplicate records have been cleaned up. Confirm the affected records and the supported correction method with the account owner or HYROS support before editing historical sales. Keep an audit trail of any correction.
- A new authorized payment produces one intended sale.
- A controlled retry of the same event does not add another sale.
- A distinct renewal or second purchase still appears.
- The amount, currency and transaction relationship remain correct.
Frequently asked questions
Can I deduplicate using the customer email?
Email alone is not a transaction identifier. One customer can make multiple purchases, installments or renewals. Use the actual business transaction and the integration’s documented behavior.
Does fixing Meta event duplication fix HYROS sales too?
These are separate destinations. Verify the records and deduplication behavior in each destination; a successful test in one does not prove the other is correct.
Will disabling an integration remove old duplicates?
Do not assume that it will. Verify new event delivery first, then review historical correction as a separate, authorized task with a record of what changes.
REVIEW YOUR SETUP
Turn the question into a clear next step.
Share your website or funnel and the problem you see. The team emails your free initial report within 24 hours. We identify what could be checked and what needs further evidence.
Get my free HYROS reportThe $499 USD deep audit and implementation have separate scopes. VIXI is an independent agency specializing in HYROS.