Skip to main content

Account Settings

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

Account Settings

Account Overview#

There are four type of setting for Account:

  • My configurations: there you can customize your Console and update your password.
  • Company's configurations: it is a must to provide all the information requested there before using Tuna's solution in production.
  • Developer: there you will find technical information, such as credentials and endpoints.
  • Users: there you can grant access to Console to new users, if you have Admin role.

Developer#

You can start the integration of Tuna's solution into your app or website as soon as you have your Tuna account. In the Developer section, you will find the technical detail needed:

Tuna Credentials#

You must use your Tuna credentials to integrate either via Plugins & SDK's or API Rest. Your credential is composed of three elements: app token, account, and account id. In case you don't include the correct keys located in your Developer section, your application will receive an error when trying to use Tuna's solution.

Webhook for asynchronous callbacks#

Tuna uses webhooks to notify your application when an event related to your payment transactions happens. Webhooks are particularly useful for asynchronous events like payment confirmation from a bank, payment cancellation via Console, and chargeback notifications.

Webhook settings:

  1. Create a webhook on your server.
  2. Register the endpoint in Tuna Console in the Developer section.

Best Practice:

  • Security: Include an authentication for this integration to prevent attacks. Keeping your endpoints secure is critical for protecting your customers's information.
  • Notification Types: Configure webhook endpoints to receive only the methods required for your integration. Listening for additional events (or all events) will put undue strain on your server and it is not recommended.

Users#

Each user can be assigned to one or more accounts, but can have only one role that is applicable to all accounts. Each role has a set of permissions, as described below:

Role NameDescriptionPermissions
AdminBest for business owners and company administratorsRefund transactions, Edit Messages, Edit Service, Edit Flows, Create Users, See tuna credentials
Read OnlyBest for people who need to view data and download reports, but do not need to make changes.Can only read information that is not sensitive
Finance SpecialistBest 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, Can not edit Messages, Edit Service, Edit Flows, Create Users, Can not see tuna credentials
TI SpecialistBest 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, See tuna credentials