/**
 * Where the withdrawal has got to. One value rather than a set of booleans:
 * `settling` and `requested` differ only in whether anything of ours is still
 * being watched, and as flags they could both be set at once.
 */
export type WithdrawalStatus = 
/** Ours is on-chain and still settling. */
'settling'
/** A venue accepted it; there is nothing of ours left to watch. */
 | 'requested' | 'complete'
/** The relay reported a terminal failure — not merely a slow settle. */
 | 'failed'
/** Failed, and the funds are on their way back to the sender. */
 | 'refunded';
export interface WithdrawCompleteScreenProps {
    status: WithdrawalStatus;
    /** What left the account, for the copy a failure needs. */
    amountLabel: string;
    /**
     * What arrived, frozen at submission — the quote is long gone by now, so
     * `undefined` means it was never priced rather than not priced yet.
     */
    usdLabel: string | undefined;
    tokenLabel: string | undefined;
    onDone: () => void;
}
/**
 * The outcome of a submitted withdrawal, on the figure the recipient step ended
 * on: the amount stays where it was and the chrome around it is gone, so
 * arriving here reads as the same screen settling rather than a new one.
 *
 * A missing or slow record reads as "still settling" rather than a failure — it
 * is written best-effort and the funds have already moved — but an explicit
 * terminal failure is shown as one.
 */
export declare function WithdrawCompleteScreen({ status, amountLabel, usdLabel, tokenLabel, onDone, }: WithdrawCompleteScreenProps): import("react").JSX.Element;
//# sourceMappingURL=WithdrawCompleteScreen.d.ts.map