Payments settings

Manage the public key and webhook URIs for your payments integration in Console.

The Settings page within the Payments section on Console contains essential configurations for your payments integration.

📘

Changes only apply to one app at a time

When you change the settings on this page, they apply to the app that you currently have open only.

To change the settings of a different app, open the app that you want to make changes in. Click the name of your app in the top bar to open the dropdown menu and select the app that you want to open.

The **Payments > Settings** page, where you upload your public key and set your webhook URI.

The Payments > Settings page, where you upload your public key and set your webhook URI.

Signing keys

To securely sign your API requests made through your payments integration, you need to upload a public key for your application. You send a corresponding private key with payment requests: the keys together enable you to authenticate.

To upload a public key:

  1. Click the + button to the right of the Signing keys section.
  2. In the system dialog that displays, select your public key file.

You can upload multiple public keys. Once you've uploaded a key, you can:

  • Copy your KID to your clipboard by clicking the Copy to clipboard icon to the right of it.
  • Click the bin icon to the right of your public key to delete it from your app.
  • Click the download icon to the right of your public key to download a copy.

Webhook URI

You can specify a webhook URI for your payments integration. Use this to receive webhook notifications, which you can use to monitor your payments. Each application and client_id can only have one webhook URI for payments.

To specify your webhook URI:

  1. Click the edit icon to the right of the example webhook URI.
  2. Enter a webhook URI.
    This must be in a valid URI format.
  3. Click the tick icon to the right of your URI to confirm your selection.