QUICKTXN / DOCUMENTATION
Migration guide
Move one boundary at a time: endpoint, credential, then old-access retirement.
Existing Columbus customers
Keep ore.rh.quicktxn.com until you receive a confirmed migration notice. It currently serves Columbus. A verified Columbus endpoint will make that geography explicit. New operator canaries such as col-1.rh.quicktxn.com are not customer endpoints until onboarding confirms them.
Credential migration
- Support confirms the existing QuickTxn account, chain grants, limits, and fee agreement.
- You receive a scoped replacement
hmqt-key through a secure channel. - Test the new key with the assigned QuickTxn endpoint and approved fee flow.
- Update clients during the agreed overlap and verify responses and receipts.
- 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.
Oregon becomes Oregon
Customers that require Columbus must move to its confirmed regional URL before the existing Oregon alias changes location. Actual Oregon deployment, canary validation, and the customer cutover notice happen before that switch.