/**
 * "message us" contact link appended after a submit error. Must carry a destination — an `onClick`
 * (host routes to its messages view, renders a `<button>`) or an `href` (renders an `<a>`) — so the
 * link is never rendered dead. Legacy always linked to the messages route; the DS is router-agnostic,
 * so the host supplies the destination instead.
 */
type PaymentErrorContactLink = {
    /** Link text. Defaults to "message us". */
    label?: string;
    /** Text joining the message and the link. Defaults to " Please " (use " or " for declines). */
    prefix?: string;
} & ({
    onClick: () => void;
    href?: string;
} | {
    href: string;
    onClick?: () => void;
});
/**
 * Order/submit-level failure (e.g. a declined charge). The host maps its raw error to this shape;
 * the component owns the presentation — danger color, the optional "message us" contact link, the
 * join word and trailing period — so the treatment is consistent and can't be mis-styled upstream.
 */
export type PaymentSubmitError = {
    /** The message, e.g. "Something went wrong." or an API-provided reason. */
    message: string;
    /** When set, appends "<prefix> <label>." as a contact link after the message. */
    contact?: PaymentErrorContactLink;
};
export type PaymentSubmitErrorMessageProps = {
    error?: PaymentSubmitError;
};
/**
 * Renders an order/submit-level error as "<message><prefix><link>." in the danger treatment. Shared
 * by PaymentSection (under the inline CTA) and StickyFooter (under the floating CTA) so the same
 * failure shows wherever the user submitted from, and the "message us" link can't be styled wrong by
 * the host — it only supplies the message + handler. Renders nothing when there's no message.
 */
export declare const PaymentSubmitErrorMessage: ({ error }: PaymentSubmitErrorMessageProps) => import("react").JSX.Element | null;
export {};