QUICKTXN / DOCUMENTATION

Migration guide

Move one boundary at a time: endpoint, credential, then old-access retirement.

Use your assigned endpoint

Keep the QuickTxn URL assigned to your account until support confirms a replacement. Planned regional names are not working endpoints.

Credential migration

1. Support confirms the existing QuickTxn account, chain grants, limits, and fee agreement.
2. You receive a scoped replacement hmqt- key through a secure channel.
3. Test the new key with the assigned QuickTxn endpoint and approved fee flow.
4. Update clients during the agreed overlap and verify responses and receipts.
5. Retire the old QuickTxn credential after support confirms it is no longer needed.

If you also use Sherwood Express, keep its separate credential. Do not revoke an old credential still required by that integration without a coordinated replacement.

Endpoint migration and rollback

Check chain ID, connectivity, discovery, and a controlled submission before redirecting traffic. Keep an explicitly approved QuickTxn fallback through DNS TTL and connection drain. A DNS update does not move established keepalive connections. Rollback must preserve account revocations and product separation.