Skip to main content
For the social logins and email authentication methods, by default, Circle presents your user with a UI to preview the transaction or signing details before sending transactions or signatures onto the blockchain. These confirmation UIs are applicable to the following APIs: You can customize various elements of the UIs, which enables your application to deliver context for on-chain actions.
NOTEConfirmation UIs are not available for the PIN authentication method. With PIN, you can fully customize the transaction and signing details pages while we provide a SDK UI for users to enter a PIN for authorization purposes. For more, see Authentication methods.

​
Predefined confirmation UIs

These confirmation UIs are predefined by Circle. The following example shows the UI for confirming an outbound transfer on the web app:
There are some nuances to consider in regards to the confirmation UI customization:
  • From and To addresses: Circle masks addresses so that only the first and last five digits are displayed. You can pass a string to personalize these addresses, such as “John’s Solana wallet.”
  • Fiat currency amount: This field is optional and is only displayed if configured. To configure it, you define the exchange rate to calculate the fiat currency amount, and then pass the amount to the SDK.
  • Network Fee: This is an optional field and is only displayed if passed to the SDK. You can send a POST request to the /createtransferestimatefee or /createtransactionestimatefee endpoints to get the estimate fee and pass the fee in the response to the SDK for display. If you offer an SCA wallet with paymaster functionalities, you can pass a string, such as “sponsored by Circle.”

​
Example customizations for confirmation UIs

For detailed instructions on customizing UIs for web, iOS, and Android, see the following docs: Below are examples of customizations for confirmation UIs for an outbound transfer, contract execution, and sign message or typed data:

​
Outbound Transfer

The following table shows which UI elements can be customized based on the example:

​
Contract Execution

The following table shows which UI elements can be customized based on the example:

​
Sign Message or Typed Data

The following table shows which UI elements can be customized based on the example:

​
Sign Transaction

​
Sign Raw Transaction

​
Full UI Customization

To use your own UIs, you can opt out of Circle’s predefined confirmation UIs.
  1. From the Circle Developer Console sidebar, select Configurator > Wallet Security Settings.
  2. Toggle the Confirmation UIs setting off to disable confirmation UIs.
CAUTIONYou may want to opt out of Circle’s confirmation UIs to further streamline your application’s user experience. Perhaps signature details are difficult for your users to understand or transaction confirmations, which are required for every transaction, interrupt your application’s flow. This can especially be the case for gaming applications.
While you may want to opt out of Circle’s confirmation UIs, it is highly recommended that you enable them to strengthen the security of your application for your users. If you decide to disable it, it means you can submit transactions on behalf of your users without their consent; therefore, you must provide context or disclaimers on your application that your users must acknowledge.