Going to Mainnet - StellarX402

Moving to mainnet is a config change. It is also an irreversible commitment to accepting real value. This is a short checklist to make sure the flip is boring.

Pre-flight

The flip

 requirePayment({
   facilitator: "https://facilitator.stellarx402.com",
-  network: "stellar:testnet",
+  network: "stellar:pubnet",
-  payTo: "GABC...TESTNET",
+  payTo: "GXYZ...MAINNET",
   scheme: "exact",
   amount: "5000",
   asset: "USDC",
   ...
 });

Restart. Confirm the first paid request settles into your mainnet address.

Post-flip

Watch the first hour of settlement latency. If it climbs above 15 seconds, escalate before it affects users.
Watch the rejection code distribution. A sudden spike in network_mismatch means clients are still signing on testnet.
Update any hardcoded testnet references (docs, examples, integration tests).

Rolling back

If the mainnet endpoint misbehaves, flip the config back to testnet and take mainnet traffic offline (405 or maintenance page). Do not leave a broken mainnet listing in the Bazaar; delist it explicitly. See Verifying Your Listing.