Skip to main content

Account Settings

Set up your account to start submitting your payment transactions with Tuna.

Account Settings

Account Overview#

Once you have your Tuna account, you will have the options below for your Account Settings:

  • Profile: Customize your Console and update your password.
  • Users: Grant access to new users. This option is only available to Admin users.
  • Company: Inform your billing information. This is a must for going live with Tuna.
  • Integration: Inform how you will integrate with Tuna and get your Tuna credentials.
  • Webhook: Inform the URL of the endpoint of your webhook (if applicable).


Inform how your website will be integrated with Tuna to get your Tuna Credentials. The steps required in this section can vary for each integration. Don't forget to click on Save at the end of the page to update your settings.

Please check out the steps applicable to your integration.

Tuna Credentials#

They are composed of a key and a token.

Except for VTEX, you will have two options for your credentials: one is by partner level, and the other is by account level. The difference between them is how you want to tokenize the card data among your accounts. If you don't have two or more accounts, we recommend using account level credentials.


The webhook setup is important to keep your website updated regarding the asynchronous events of your payments, such as:

  • payment confirmation;
  • chargeback;
  • cancellation;

among others. For platforms, such as WooCommerce and Magento, the URL is usually:

{your website}/?wc-api=tuna_payment_callback

This section is not applicable for VTEX, since the webhook setup is already defined in the plugin integration.

If you use the integration through APIs, you must create an endpoint for the webhook on your server:

  • Authentication: include an authentication to prevent attacks and keep your customers' information secure.
  • Methods: define which type of events you want to notify your website. Ideally, it would be best to define only events relevant to your website to avoid undue strain on your server. However, if you don't know which of them are relevant, we recommend selecting all available options.


Each user can be assigned to one or more accounts. But this user can have only one role that will apply to all accounts.

Each role has a set of permissions, as described below:

Role NameDescriptionPermissions
AdminBest for business owners and company administrators.Refund transactions, Edit Messages, Edit Service, Edit Flows, Create Users, Access to Tuna credentials.
Read OnlyBest for people who need to view data and download reports but do not need to make changes.Read information that is not sensitive.
FinanceBest for finance, risk, and payment areas. People who need full access to information and create new elements but can't publish them in production.Refund transactions, See Messages, Edit Service, Edit Flows, Create Users.
TechnologyBest for developers or product owners that work with API, only roles that can publish in production.Refund transactions, Edit Messages, Edit Service, Edit Flows, Create Users, Access to Tuna credentials.
Customer SupportBest for people who work with payment refunds and general customer support.Refund transactions, Read the information that is not sensitive.