Console
The solution that help you to manage your online payments, with out coding a line! Just plug your service in, and start tunning your flows. Here you can feel safe testing your hypotesis before making big changes that can afect the key metrics of your company. 😌
Get your Console access
Once you have your Tuna account, you will receive Console access. Look for the update password email on your box.
For your safty the URL to access will be: http://console.tuna.uy/{companyname}.
Account Settings
Set up your account, so you can start transacting with Tuna. In this section you will find:
- Profile Information: Customize your Console platform.
- Company Information: Please compleate this information before going to production.
- Developers Settings: Information needed to build your integration with us.
- Users: Create new users to give Console access inside your company.
Developer Settings, a quick start.
Integrating Tuna into your app or website can begin as soon as you create a Tuna account, and you will find what you need at the Developer Setting Section:
- Obtain your Tuna Credentials, so we can authenticate your integration in production.
- Set up your Webhook for asyncronus callbacks, so we can mantain you updated of any status changes in your payment transactions.
Tuna Credentials
Tuna authenticates your requests using your account’s information. If you don’t include your key when making any API request, or use one that is incorrect or outdated, Tuna Payment API returns an error. This information will also be requested in any of our plugins integrations. (link)
Your Tuna Credentials are always available in the Developer Settings at Console. They are composed by three elements: your partner key, your partner id and your partner_account.
Tuna's sandbox environment uses public keys available to anyone:
(componente com chaves sandbox)
Webhook for asynchronous callbacks
You can receive event notifications with webhook. Tuna uses webhooks to notify your application when an event happens related to your account. Webhooks are particularly useful for asynchronous events like when a customer’s bank confirms a payment, you cancel a payment transaction in our Console or we get any information about your chargebacks
Begin using webhook in two steps:
- Create a webhook in your server.
- Register the endpoint in Console Developer Settings.
Best Practice:
- Security: Keeping your endpoints secure is critical to protecting your customers's information. So please, include an autentication for this integration to prevent any atacks.
- Notification Types Your webhook endpoints should be configured to receive only the methods required by your integration. Listening for extra events (or all events) will put undue strain on your server and is not recommended.
Transactions
What is a payment method?
Service Providers
Tuna allows you to integrate with many services: payment gateways, antifraud systems and more. You can easily set them up by the Console.
Here you can check all the integrations we have already develop. (LINK)
General steps for integration:
- Open an account with the service provider.
- Get your production keys.
- Set up the service in Console.
- Include the prodiver in a Flow.
If you dont know how to open an account in the service provider, you can check than information in this guide. (LINK)
Set up the service
In Console side bar you will find the Service section. There you can find all the integration we had already developed. You will also have a highligthed section with the most popular service in your country. With a scroll you can find a button that allows you to go to all service list order by name.
If you are trying to find a provider that is not on our list, or if you need a request that is not already implemented: you can contact us and we will work for it. We always try to prioritize our work to help our customers! 🤗
Steps to include a Service:
- Select de service.
- Include Service Configuration. For each service you might be able to set up diferent things. Check up our service guide. (LINK)
- Save. At this moment we will make a test to make sure your keys are correct.
- Include your Service's Fees.
Common Errors when including Service:
- Check that the Service Keys that you are including are for Production Enviroment.
- Remember to check if needed to activate any specific payment method: Boleto, PIX, etc.
- Dont forget to include the service in a Flow! You can always check on your Service Card if the Service is already link to a flow.
Service's Fees
This information is very important to calculate how this service cost is impacting your company revenue. You can find this information at you service account provider. You must update any time they change. We will save each version, to calculate correctly the fee of each transaction.
Also with this information, we are able to check if what you agreed with the service provider is the same that you are beeing charged.
Flows
Once you have your Service setted up, you need to create at least one Flow to start transacting with Tuna. This first new flow we will call it: Default Flow. But, we encourage you to think as many diversification flows as you think will be needed to have an optimized payment solution.
If you have any doubts about how our online payments work, you can check more information here. (LINK)
In the side bar menu you will find a tab call Flows, go there so you can start! 🚀
What is a flow?
A Flow is the way you can determinate to Tuna how you want a payment transaction to move along between your services.
Every flow must have this two templates:
- a filter section: set of atributes that define which transactions will go walk through that Flow.
- an Authorization Scheme: one or more payment service stratergies to get your transaction approved to start.
You can also include optionally other templates:
- antifraud analysis and actions: when your transactions needs an antifraud approval, and what is needed to be done with the antifraud response.
- challenges: sometimes is needed to have more information about your user to make a save transaction, in that case our challlenges will help you.
- custom features: if you need, we can also develop a custom integration for your flow.
Here you can see some flows examples. (LINK)
Filters
When you create a new flow, you need to include an especific filter to determinate which transactions will go through it. You can combine them, and also each filter have many operators.
For example you are able to create a filter like this one: If tranaction matchs with: Category.Name in Smartphones, Alcohol Drinks and Payment.Amount greater than 1.000,00.
We can handle this filters:
| Filter Name | Type | Description |
|---|---|---|
| Category.Name | String | Item category. Ex: Smartphones. |
| Operating.System | String | User Operating Sistem. Ex: iOS, Android. |
| Login.Type | String | How user login in your site. Ex: Google Login. |
| Payment.Amount | Number (double) | Value the user pay on this transaction. Ex: $100,00 |
| Method.Amount | Number (double) | Value the user pay with an specific payment method. Ex: $80,00 |
| Installments | Select | Number of Istallements on this transaction. Picklist. |
| Payment.method.type | Select | Name of the payment value. Ex: CreditCard. |
| BIN | Number | User Card Bank infentification Number. Ex: 4040. |
| Brand.Name | String | User Card Brand. Ex: Master, Visa, Amex. |
| Customer.Email | String | User Email on this transaction. Ex: tinaturner@tuna.uy |
| Address.State | String | User Billing Address State. Ex: SC. |
| Address.City | String | User Billing Address City. Ex: Florianópolis. |
| Address.Postal_code | Number | User Billing Adress Postal Code. Ex: 88035320 |
| Custom.name | String | You can set up any custom value from your integration. Ex: Custom.userid |
Authorization Scheme
Here you will determinate how the authorization of your payments will work. You can create an Authorization Scheme once you have at least one Payment Service added in your Console.
Authorization is the process to check whether or not a transaction can be made. At this time, several checks are made with the payment method and the user (eg, payment, blockages, etc.) It is also at this time that the card limit is sensitized to the value of the transaction. With Tuna you can choose when this authorization will happen by allocatin the Authorization Scheme template in your flow.
Sometimes the service you are trying to use for autorization is not responding, or is rejecting your transaction. For that, you can include up to two retrys in your authorization scheme, so we can doble check if the transaction is suspicious. This will help you to have a better approval rate.
If you are working with more than one payment service, and you want to make shure how many transaction go through each service you can allocate the percentage of transaction for each one.
You might want to set up an especific authorization scheme for a payment method or card brand. For example, if your Service Fee of VISA is better in an especific Payment Service, you can allocate all VISA transaction on it with an specific Authorization Scheme.
Here you can see some Authorization Scheme examples. (LINK)
Antifraud Analysis and actions
An anti-fraud solution is a prevention system that aims to prevent a online business from suffering financial losses. It works to detect a threat, whether by a real person or bots, and stop it before it consummate the attack.
Antifraud will help you to reduce your fraud fees.
You can include Risk Analysis once you have at least one Antifraud Service added in your Console.
Then you can set up Actions to treat the Antifraud response, and define whenever you feel save to capture the payment (or not).
Here you can see some Flows with Antifraud examples. (LINK)
How flow list works?
Onces you create more than one flow, you will to indicate the priority that they have: drug and drop them to order them. When we start a transaction we will go through every filter determinated in your flows to alocate in the correct payment transaction flow, in the order that you have determinate.
Remember, if your transaction doesn't match with non of the filters you have determinated, we will transact it with your Default Flow. That is why Default Flow is always going to be fixed at the bottom of you flows list.
Flow Metrics
In your Flow List you can find five métrics. They are beeing calculated frequently so you can track how your payment solution is. This metrics are calculated based on the Payment Method of your transactions.
Net/Attempted
This metric tells you how much many you get, over $1 transacted in that flow. The closer you get to $1, the optimum your flows are. To calculate it we take into account the approved rate, the fees and fraud cost envolved in that Payment Method transaction.
Transactions
This metric shows how the Payment Method transactions are allocated between your flows. If you add all transaction percentile, you get 100%.
Approved
This metric express how many Payment Method transactions are approved, from any transaction iniciated in that flow.
Fees
We save every Service's Fees for each Payment Method transaction. And on this metric we calculate for all the amount transacted in that flow, how much percentile you have spent in Service's Fees.
You might not have information in this metric, if you dont have all your Service's Fees with information. Remember to fill this information and keep it updated.
Fraud Costs
Here definition
AB testing
A/B tests consist of a randomized experiment with two flow variants, A and B. You should use this feature when you want to test an hypotesis. For example: I think Payment Service Provider X, will approve more and is cheaper than Service Provider Y. Even if you think your hypotesis is self-evident, we suggest always to test before making flows changes.
To allocate the transacions in the AB Test Flow we use simple random sampling. And also we leave a grup of control, so we can check the sampling is not beeing biased.
Create AB Test
Once you have at least one flow created, you are able to create a test.
To start the AB you will need to define your hypotesis, and the trafic allocation you want to start with. Then you will determinate the B flow, where your hypotesis is going to be test. You are able to remove, re-order and change every flow template.
Once your flow is publish, you are going to able to see the results of this test. As any AB test, to have a statistical relevance you need time and transaction volume. So do not draw conclusion quickly.
When your test reaches statistical relevance, you will be able to promote you B flow or archive the test, and continue with flow A.
(levar isso para outra pagina) Click a provider below to view its specifications.
If you are trying to find a provider that is not on our list, or if you need a request that is not already implemented: you can contact us and we will work for it. We always try to prioritize our work to help our customers.
| Name | Service Type |
|---|---|
| Cielo | Payment |
| Rede | Payment |
| Adyen | Payment |
| Paypal | Payment |
| Midway | Payment |
| Boleto Santander | Payment |
| Boleto Bradesco | Payment |
| Omnipay | Interceptor |
| Braspag | Interceptor |
| Mundipagg | Interceptor |
| Getnet | Interceptor |
| Clearsale | Antifraud |
| Cybersource | Antifraud |
| Konduto | Antifraud |
| Sift | Antifraud |
| Sitef | Authorizer |
Cielo
Request that are supported:
- Sync Payment Authorization
- Async Payment Capture
- Cancel payment
- Consult Payment Status
Request that are not already developed:
- Process chargebacks
Payment Methods that are supported:
- Boleto
- Visa
- Master
- Amex
- Elo
- Diners
- Cabal
- Hipercard
- Sorocred
- Agiplan
- Banescard
- Credsystem
- JCB
- Credz
Rede
Request that are supported:
- Sync Payment Authorization
- Async Payment Capture
- Cancel payment
- Consult Payment Status
Request that are not already developed:
- Process chargebacks
Payment Methods that are supported:
- Boleto
- Visa
- Master
- Amex
- Elo
- Diners
- Cabal
- Hipercard
- Sorocred
- Agiplan
- Banescard
- Credsystem
- JCB
- Credz
Adyen
Request that are supported:
- Sync Payment Authorization
- Async Payment Capture
- Cancel payment
- Consult Payment Status
- Callback for cancellations
- Process chargebacks by callback
Request that are not already developed:
- 3DS
Payment Methods that are supported:
- Visa
- Master
- Amex
Paypal
Request that are supported:
Request that are not already developed:
Midway
Request that are supported:
Request that are not already developed:
Payment Methods that are supported:
Boleto Santander
Request that are supported:
Request that are not already developed:
Boleto Bradesco
Request that are supported:
Request that are not already developed:
Omnipay
Request that are supported:
Request that are not already developed:
Braspag
Request that are supported:
- Sync Payment Authorization
- Async Payment Capture
- Cancel payment
- Consult Payment Status
Request that are not already developed:
Payment Methods that are supported:
- Visa
- Master
- Amex
- Boleto (Bradesco, Banco do Brasil, Itaú Shopline,Santander, Caixa economica, e Citibank.)
Mundipagg
Request that are supported:
Request that are not already developed:
Payment Methods that are supported:
Getnet
Request that are supported:
Request that are not already developed:
Payment Methods that are supported:
Clearsale
Risk Analyst request that are supported:
- Score
- Probe Status
Request that are not already developed:
- 3DS
Cybersource
Risk Analyst request that are supported:
- Score
- Probe Status
Request that are not already developed:
- 3DS
Konduto
Risk Analyst request that are supported:
- Score
- Probe Status
Request that are not already developed:
- 3DS
Sift
Risk Analyst request that are supported:
- Score
- Probe Status
Request that are not already developed:
- 3DS