Monitor X402 Payments & Reconcile Settlements

This guide walks you through monitoring incoming X402 payments and reconciling them against application orders, so you can catch discrepancies early and keep your financial records accurate. You’ll learn how to track payment statuses, match settlements to orders, and resolve mismatches systematically.

What You’ll Need

• Access to the X402 payment dashboard or admin panel
• Your application’s order management system (OMS) or database
• A list of today’s or the period’s order IDs and amounts
• Spreadsheet software (Excel, Google Sheets) or a reconciliation tool
• Permission to export payment and order data

Step-by-Step

1. Log in to your X402 merchant dashboard. Navigate to the “Payments” or “Transactions” section. Set the date range to match the period you’re reconciling (e.g., today, last 7 days, or a specific business day).
2. Export the payment settlement report. Look for an “Export” or “Download” button (usually CSV or Excel). This report should include: transaction ID, order reference (if provided), payment date/time, gross amount, fees, net amount, and status (e.g., settled, pending, failed, refunded).
3. Export your application’s order data. From your OMS, export orders placed during the same period. Include order ID, order date, total amount, payment status, and any payment gateway reference if stored.
4. Prepare a reconciliation spreadsheet. Create two tabs: one for “X402 Payments” and one for “Application Orders.” Paste the exported data into each tab. Ensure columns are aligned (e.g., amount, date, order reference).
5. Match payments to orders. Use the order reference or transaction ID to link each X402 payment to its corresponding order. If your system doesn’t store a reference, match by amount and date (be careful with same-day duplicates). In Excel, you can use VLOOKUP or Power Query; in Sheets, use VLOOKUP or QUERY.
6. Identify unmatched payments. Filter for X402 payments that don’t have a matching order. These could be: payments without an order (e.g., manual entry), duplicate payments, or payments with incorrect reference numbers.
7. Identify unmatched orders. Filter for orders that don’t have a corresponding X402 payment. These may be unpaid orders, orders paid via other methods, or payments that haven’t settled yet.
8. Check statuses. For matched pairs, verify that the payment status in X402 matches the order’s payment status in your application. For example, if X402 says “settled,” the order should be “paid.” If X402 says “pending,” the order should still be “awaiting payment.”
9. Reconcile amounts. Compare the net amount (after fees) from X402 with the order total. Note that fees will cause a difference; the net amount should equal the order total minus the gateway fee. If the gross amount doesn’t match the order total, investigate.
10. Record discrepancies. Create a third tab titled “Discrepancies.” List each issue: order ID, payment ID, expected amount, actual amount, status mismatch, and a brief description. This becomes your action list.
11. Resolve discrepancies. For each discrepancy, take corrective action: contact X402 support for missing payments, issue refunds for overpayments, follow up on failed payments, or update order statuses if payments settled after export.
12. Mark reconciliation as complete. Once all items are resolved or documented, save the spreadsheet with a clear filename (e.g., “Recon_2025-05-20.xlsx”) and archive it for your records.

Common Mistakes

• Matching by amount only when multiple orders have the same total, leading to false matches. Always use a unique reference if available.
• Ignoring timezone differences. X402 may record times in UTC, while your application uses local time. This can cause orders to appear on different dates.
• Forgetting about fees. The settlement amount is net of fees, so comparing it to the order total will always show a difference. Always compare gross amounts.
• Not accounting for refunds. A refunded payment will appear as a separate transaction or a negative amount. Ensure your matching logic handles these.
• Exporting only settled payments. Pending or failed payments also need reconciliation. Include all statuses in your export.

Tips

• Automate where possible. If your volume is high, consider using a reconciliation tool or writing a script to match payments and orders automatically.
• Use unique order references. When creating orders, pass a unique order ID to X402 as the reference. This makes matching trivial.
• Reconcile daily. Daily reconciliation prevents backlog and makes it easier to identify issues while they’re fresh.
• Keep a template. Create a standard spreadsheet template with formulas pre-filled to speed up the process each day.
• Document your process. Write down your steps and share them with your team so everyone reconciles consistently.

Troubleshooting

Payment appears in X402 but not in your application. First, check if the payment is pending or failed. If it’s successful, the order may have been created but the payment callback failed. Manually update the order status or contact support.

Order shows as paid but no X402 payment. This could mean the payment was made via another gateway, or the order was marked paid manually. Verify with the customer and check your gateway logs.

Amounts don’t match. Double-check if taxes, shipping, or discounts were applied correctly. Also ensure you’re comparing gross amounts, not net.

Duplicate payments. If a customer paid twice, you’ll need to issue a refund for the duplicate. Contact X402 support to process the refund.

Export fails or times out. Try narrowing the date range, or export in smaller batches. If the issue persists, check your internet connection or contact X402 support.

Frequently Asked Questions

How often should I reconcile X402 payments?

Ideally daily, especially if you have high transaction volume. At minimum, do it weekly to catch issues early.

What if I don’t have an order reference in X402?

You can still match by amount and date, but be extra careful with duplicates. Consider adding the reference in future integrations.

Can I reconcile automatically?

Yes, many payment gateways offer APIs that allow you to fetch payment data programmatically. You can build a script to compare with your database.

What does “settled” mean in X402?

Settled means the funds have been transferred to your bank account. Pending means the payment is authorized but not yet captured.

How do I handle refunds in reconciliation?

Refunds appear as negative amounts or separate transactions. Subtract them from your gross settlements and ensure the corresponding order is marked refunded.

What if I find a payment with no order at all?

This could be a test transaction or a payment where the order creation failed. Contact X402 support to investigate, and consider refunding if it’s not legitimate.

Related

• Loom vs Scribe: Which Matches Your Workflow?
• Payment Options for Small Businesses in India Besides UPI
• Offshore Hosting: What It Is & How to Choose