Run the issuer, every action on record
The back office is where an operator runs the issuer on Stellar Testnet: attribute or return a stray wire, freeze a holder, watch the mint buffer, and reconcile the ledger against the chain. Every screen is live on Testnet, drawn from the same capabilities manifest as the capabilities page.
Attribute a deposit, with a reason
Who does this wire belong to?
A wire with no reference lands in suspense. Before it is credited, the operator names the organisation and records a reason for the audit log.
Transcript
When a wire arrives without a reference, it lands in suspense until an operator attributes or returns it. This 18,500 USD wire had no reference, so it wasn't credited to anyone. It waits here until Omar acts. Northwind confirms it sent the wire, so Omar attributes it to Northwind's organisation, with a reason for the audit log. The money is credited to Northwind. Had he picked a matching mint, that mint would carry on. A wire nobody can claim goes back instead: Omar requests a return to the sending bank, again with a reason. USDX paid to the platform's plain Stellar address, with no muxed ID, lands here too, and can only go to a matching redemption.
Transcript
The issuer can freeze a holder so they can't move USDX, and every freeze needs a case and a reason. Omar enters the holder's Stellar address, here Partner A, a case reference, and a reason for the audit log. Before he requests it, the screen shows the exact operation the issuing account will sign: SetTrustLineFlags, clearing AUTHORIZED. The signing service signs it, and the case reads frozen only once Stellar confirms. Partner A's 15,000 USDX can't move, but stays in supply. Releasing works the same way: another reason, and an operation that sets AUTHORIZED again. Anyone can see this power on the transparency page: the issuer can freeze holdings, but can't claw them back.
Freeze a holder, and show the operation
What will this freeze sign?
Before an operator confirms, the screen shows the exact Stellar operation the issuing account will sign: SetTrustLineFlags, clearing AUTHORIZED.
Reconcile the ledger, against the chain
Does the ledger match the chain?
Every five minutes four checks run: supply against the chain, reserves against supply, the bank against the ledger, and how fresh each reserve source is. A Sev-1 break pauses mints on its own.
Transcript
Reconciliation checks that supply, reserves and the bank agree, and pauses mints when supply or reserves don't. Every five minutes it runs four checks: supply against the chain, reserves against supply, the bank against the ledger, and how fresh the reserve sources are. At 3:00 PM the chain shows 250 USDX more than the ledger expects. Supply is a Sev-1 check, so mints pause on their own. Omar runs reconciliation on demand, with a reason for the audit log. This run is clean, but mints stay paused. Resuming is a separate step with its own reason. It doesn't fix a break: if a Sev-1 break persists, the next run pauses mints again. USDX is minting again, and the 3:00 PM break stays under Recent breaks.