Legal Agreements Support
We also provide a version of this page in Portuguese (PT-BR) to support our legal agreements. Click here to access this page.
The defined Pix pricing for the integration of the Dock PartnerDock Partner - Dock Partners are companies using Dock services in a BaaS model. using the Banking as a Service (BaaS) or Fintech as a Service (FaaS) model is presented below.
All mentioned amounts are in BRL and net of taxes, which means they do not include taxes. Therefore, the applicable direct taxes should be added to the amount, i.e., an additional 11.25% for ISS, PIS, and COFINS.
All Dock Partners with accounts issued by Dock as a Payment Institution and Alias Accounts of any Brazilian Payment System Identifier (ISPB) or simple transactional accounts are considered BaaS clients. The pricing for Dock Partners using this model, regardless of whether they use the Alias Bank accounts or the simple transactional account model, is described below.
The transaction cost is applicable for credit transactions (receiving funds from other institutions) and debit transactions (sending funds to other institutions), regardless of being a natural or legal person, the origin or destination of the funds.
There is no charge for transactions with origin and destination within the Payment Institution Dock.
Plans for Batch Reservation: BaaS Partners can select one of 5 (five) batch reservation plan options, which vary in time and cost. This planning assists Dock with the scale of its Pix providers and also makes it possible to offer pricing savings. Check out the options below:
Number of Transactions (Month)
Implied Unit Cost / Transaction (BRL)
Up to 25,000
Up to 75,000
Up to 312,500
Up to 1,5M
Up to 5M
All plans can be renewed for additional 3 (three) months.
Every transaction above the selected plan will incur an additional charge of BRL 0.30.
There is an additional anti-fraud fee of BRL 0.05 per credit and debit transactions.
- Authorization ("Authorization" item): Costs applied to debit transactions, according to Agreement with the Dock Partner / Dock Client. It does not apply to credit transactions.
Anti-fraud ("Transactional Anti-fraud" item): Dock's anti-fraud tools (Falcon RBTran and/or Sherlock) are charged according to each credit and debit transaction. The amount will be charged according to the current Agreement with the Dock Partner / Dock Client. The billing method now includes all transactions: debit and credit. The previous method included only debit and it has been changed.
Anti-Fraud Treatment ("Anti-Fraud Treatment" item): Refund applied to each case treated, according to the Agreement with the Dock Partner / Dock Client.
- Issuance of dynamic QR Code not yet settled (not paid): BRL 0.10 per QR Code issued;
- DICT query (GET method, Validate Pix DICT Keys endpoint) outside the context of a payment transaction:
- BRL 0.25 per GET method, for the first 1000 monthly requests;
- BRL 0.50 for requests that exceed this first 1000.
The defined transaction costs may be adjusted according to the positive or negative variation of whole chain prices, fees, charges, and other expenses related to the referred payment transactions, including, but not limited to, the rates applied by the Central Bank of Brazil (BACEN).
Transactional costs will be adjusted annually by the positive variation of the Consumer Price Index (IPCA), or any other index which may replace it.
All Dock Partners who are either Indirect or Direct Pix Participants are considered FaaS clients. The pricing for Dock Partners using this model, regardless of whether they are Indirect Participants with Dock integration for Direct Participants or Direct Participants with Dock integration for Information Technology Service Providers (PSTI), follows the format below.
Authorization ("Authorization" item): Costs applied to debit transactions, as provided for in the Services Provider Agreement; it does not apply to credit transactions.
Anti-fraud ("Transactional Anti-fraud" item): Dock's anti-fraud tools (Falcon RBTran and/or Sherlock) are charged according to each credit and debit transaction. The amount will be charged according to the current Services Provider Agreement and only the billing method will be changed, including all transactions, and not only debit, as it is currently used.
Anti-Fraud Treatment ("Anti-Fraud Treatment" item): refund applied to each case treated, as provided for in the Services Provider Agreement, as applicable.
Transactional API Requests
Query API Requests
Cost per Webhook sent
Cost per Data Storage
BRL 0.0002 per request
BRL 0.0001 per request
BRL 0.0008 per request
BRL 6 per GB/monthly
- Transactional API Requests: Any
DELETEmethods that return HTTP status code (response)
- Query API Requests: Any
GETmethod endpoint that returns HTTP status code (response)
- Cost per Webhook sent: Any webhook sent that received HTTP status code (response)
4XXfrom the client.
The Technological Stack costs may be adjusted according to the positive or negative variation of the whole chain prices, fees, charges and other expenses related to the referred payment transactions made, including, but not limited to, the rates applied by BACEN.
Transactional costs will be adjusted annually by the positive variation of the IPCA, or another index that may replace it.
Faas Clients can use the Income Reports API to generate and send the income reports and it will be charged R$0.20 per API call. The IR PDFs will be generated by this API and the IRRF will be calculated as per definition from Dock Tax Department, according to the API documentation. Any differences or delay in payment of DARF or DIRF is the sole responsibility of the FaaS Client, and Dock is exempt from any obligation.
The (.csv) files are available free of charge to FaaS Clients and they contain the account identification (
accountId), account holder name, document, balances, income, among others. In this way, FaaS Clients can provide the IR to their account holders.
It is a technology that replaces the sensitive data of cards with an alphanumeric sequence called tokens. It allows payments to occur using tokens and without transferring any customer data. It can be acquired at Dock (click here for more details) and the corresponding prices are as follows.
This is a one-time fee charged by Dock for the setup.
Setup (one-time fee for Dock BaaS Partners)
Setup (one-time fee for Dock FaaS Clients)
This table shows the price per tier, valid for both Dock BaaS Partners and Dock FaaS Clients. The monthly cost for Dock Partner / Dock Client is calculated based on the quantity of active HCE tokens multiplied by the price of the corresponding tier:
Quantity of Active HCE Tokens
Price per Active HCE Token
Up to 100,000
From 100,001 up to 200,000
From 200,001 up to 300,000
From 300,001 up to 400,000
From 400,001 up to 500,000
More than 500,001 tokens
3DS is a security protocol used in the authentication of the cardholder during online payments, i.e., credit or debit card transactions in online purchases. It reduces fraud by authenticating the payer's identity, i.e., the cardholder’s identity in card-not-present (CNP) transactions.
Annual Fee: There will be a yearly charge of BRL 1,833.00 for the use of 3DS authentication.
It will be charged for BaaS Partners or FaaS Clients, who have Dock, as the Card Issuer.
This value will be charged in the invoicing process in the monthly billing.
Charges per Authentication: It will be charged BRL 0.64 at each cardholders' transaction (i.e. on online purchases), which has gone through the 3DS authentication.
BaaS Partners or FaaS Clients will be charged with this value in the invoicing process in their
Charges : Eligibility
At every 3DS call, there will be a charge of BRL 0,64, in spite of the result of the authentication or the transaction status. Below are just some examples:
- At invalid authentication - During the 3DS process, if the cardholder enters the wrong password, the online purchase will not complete. In this case, although the authentication had a negative result, it was executed. Thus, the 3DS event will be charged.
- For not completed purchases - During the 3DS process, the cardholder was successfully authenticated, but the purchase could not be completed, due to a lack of funds. Although the transaction was not completed, the 3DS event was executed and it will be charged.
Updated about a month ago