Documentation Index
Fetch the complete documentation index at: https://support.wepayments.com.br/llms.txt
Use this file to discover all available pages before exploring further.
Markup is a feature that allows a main merchant to generate revenue from transactions processed by their sub-merchants. It was designed for businesses that operate with franchises, partners, or any hierarchical structure where a main merchant manages the financial operation.
How Markup works
Under the markup billing model, WEpayments charges operational fees only to the main merchant. Sub-merchants do not have their own fees configured with the platform. Instead, monetization happens through a markup applied to each charge (Payin) or payout created by sub-merchants.
Simple explanation
| Step | What happens |
|---|
| 1 | Sub-merchant processes a transaction |
| 2 | System applies the defined markup |
| 3 | Corresponding amount is automatically credited to the main merchant’s wallet |
Who can use Markup?
The Markup product is available exclusively to merchants with the markup billing model enabled on their products.
Eligibility
| Criteria | Details |
|---|
| Availability | Exclusive to merchants with markup billing model enabled |
| Applicable transactions | Only transactions created by sub-merchants |
| Not applicable | Charges or payouts created directly by the main merchant |
Ideal for companies that:
- Provide payment infrastructure to partners
- Want to scale their monetization model efficiently
- Operate with franchises, affiliates, or sub-partners
- Need separate revenue streams for parent company and sub-entities
How Markup can be applied
How Markup works
Under the markup billing model, WEpayments charges operational fees only to the main merchant. Sub-merchants do not have their own fees configured with the platform. Instead, monetization happens through a markup applied to each charge (Payin) or payout created by sub-merchants.
Simple explanation
| Step | What happens |
|---|
| 1 | Sub-merchant processes a transaction |
| 2 | System applies the defined markup |
| 3 | Corresponding amount is automatically credited to the main merchant’s wallet |
Who can use Markup?
The Markup product is available exclusively to merchants with the markup billing model enabled on their products.
Eligibility
| Criteria | Details |
|---|
| Availability | Exclusive to merchants with markup billing model enabled |
| Applicable transactions | Only transactions created by sub-merchants |
| Not applicable | Charges or payouts created directly by the main merchant |
Ideal for companies that:
- Provide payment infrastructure to partners
- Want to scale their monetization model efficiently
- Operate with franchises, affiliates, or sub-partners
- Need separate revenue streams for parent company and sub-entities
How Markup can be applied
The product supports two ways of applying revenue, offering both flexibility and predictability.The product supports two ways of applying revenue, offering both flexibility and predictability.
1. Global Markup (Default)1. Global Markup (Default)
A standard rule configured at the main merchant levelA standard rule configured at the main merchant level.
| Aspect | Description |
|---|
| When applied | Whenever a transaction is created by a sub-merchant and no specific markup value is provided |
| Behavior | System automatically applies the global markup |
| Use case | Baseline monetization rule – ensures all transactions generate revenue |
2. Inline Markup
Sent directly when creating a charge or payout.
| Aspect | Description |
|---|
| When applied | Merchant defines exact markup amount for a specific transaction |
| Format | Percentage-based or fixed amount |
| Use case | Special negotiations, campaigns, specific rules by product, region, or partner |
| Priority | Always overrides the global markup for that transaction |
Global vs. Inline Markup comparison
| Aspect | Description |
|---|
| When applied | Whenever a transaction is created by a sub-merchant and no specific markup value is provided |
| Behavior | System automatically applies the global markup |
| Use case | Baseline monetization rule – ensures all transactions generate revenue |
2. Inline Markup
Sent directly when creating a charge or payout.
| Aspect | Description |
|---|
| When applied | Merchant defines exact markup amount for a specific transaction |
| Format | Percentage-based or fixed amount |
| Use case | Special negotiations, campaigns, specific rules by product, region, or partner |
| Priority | Always overrides the global markup for that transaction |
Global vs. Inline Markup comparison
| FeatureFeature | Global MarkupGlobal Markup | Inline Markup | Inline Markup |
|---|
| Configuration levelConfiguration level | Main merchant (default rule)ain merchant (default rule) | Per transaction | Per transaction |
| Flexibilitylexibility | Fixed baselineFixed baseline | Highly flexible | Highly flexible |
| Override behaviorOverride behavior | Used when no inline is providedUsed when no inline is provided | Overrides global markup | Overrides global markup |
| Best forBest for | Standard, recurring transactionsStandard, recurring transactions | Special campaigns, negotiated deals | Special campaigns, negotiated deals |
| Format | Percentage or fixed | Percentage or fixed | |
| Format | Percentage or fixed | Percentage or fixed |
What happens financially?What happens financially?
After a sub-merchant’s transaction is settled, the system automatically performs the financial allocation:
After a sub-merchant’s transaction is settled, the system automatically performs the financial allocation:
Financial flowFinancial flow
| Step | Effect |
|---|
| Markup amount deducted | From the sub-merchant |
| Markup amount credited | To the main merchant’s wallet |
| WEpayments operational fee | Charged only to the main merchant |
| Step | Effect |
|---|
| Markup amount deducted | From the sub-merchant |
| Markup amount credited | To the main merchant’s wallet |
| WEpayments operational fee | Charged only to the main merchant |
How it appears in statementsHow it appears in statements
| Statement typeatement type | How markup appearsHow markup appears |
|---|
| Sub-merchant statementSub-merchant statement | Separate line identified as “Markup” (debit)Separate line identified as “Markup” (debit) |
| Main merchant statementin merchant statement | Credit corresponding to the transaction revenueCredit corresponding to the transaction revenue |
Example scenarioExample scenario
Setup
- Main merchant: Marketplace Operator
- Sub-merchant: Seller João
- Global markup: 2%
- Transaction amount: R$ 1,000
Setup
- Main merchant: Marketplace Operator
- Sub-merchant: Seller João
- Global markup: 2%
- Transaction amount: R$ 1,000
What happensWhat happens
| Event | Amount | Who receives/ pays |
|---|
| Customer pays R$ 1,000 | +R$ 1,000 | Sub-merchant (gross) |
| Markup (2%) applied | -R$ 20 | Deducted from sub-merchant |
| Markup credited to main merchant | +R$ 20 | Main merchant |
| WE fee charged | -Variable | Main merchant only |
| Event | Amount | Who receives/ pays |
|---|
| Customer pays R$ 1,000 | +R$ 1,000 | Sub-merchant (gross) |
| Markup (2%) applied | -R$ 20 | Deducted from sub-merchant |
| Markup credited to main merchant | +R$ 20 | Main merchant |
| WE fee charged | -Variable | Main merchant only |
Net resultNet result
| PartyParty | Net aNet amount |
|---|
| Sub-merchantSub-merchant | R$ 980 (after markup)R$ 980 (after markup) |
| Main merchantin merchant | R$ 20 (markup revenue) minus WE feesR$ 20 (markup revenue) minus WE fees |
Use cases
| Business model | How Markup helps |
|---|
| Franchises | Franchisor earns from franchisee transactions |
| Marketplaces | Platform earns from seller transactions |
| Payment facilitators | Facilitator earns from sub-merchant volume |
| Affiliate networks | Network owner earns from affiliate sales |
| White-label solutions | Provider earns from partner transactions |
Use cases
| Business model | How Markup helps |
|---|
| Franchises | Franchisor earns from franchisee transactions |
| Marketplaces | Platform earns from seller transactions |
| Payment facilitators | Facilitator earns from sub-merchant volume |
| Affiliate networks | Network owner earns from affiliate sales |
| White-label solutions | Provider earns from partner transactions |
Important notImportant notes
| NoteNote | DetailDetails |
|---|
| Main merchant transactionMain merchant transactions | Not subject to markup (only sub-merchant transactions)Not subject to markup (only sub-merchant transactions) |
| Inline markup priorityInline markup priority | Always overrides global markupAlways overrides global markup |
| WE feeWE fees | Charged only to main merchantCharged only to main merchant |
| Sub-merchant feeSub-merchant fees | Sub-merchants have no direct fee configuration with WEpaymentSub-merchants have no direct fee configuration with WEpayments |
Markup is a feature that allows a main merchant to generate revenue from transactions processed by their sub-merchants. It was designed for businesses that operate with franchises, partners, or any hierarchical structure where a main merchant manages the financial operation.
How Markup works
Markup is a feature that allows a main merchant to generate revenue from transactions processed by their sub-merchants. It was designed for businesses that operate with franchises, partners, or any hierarchical structure where a main merchant manages the financial operation.
How Markup works
Under the markup billing model, WEpayments charges operational fees only to the main merchant. Sub-merchants do not have their own fees configured with the platform. Instead, monetization happens through a markup applied to each charge (Payin) or payout created by sub-merchants.Under the markup billing model, WEpayments charges operational fees only to the main merchant. Sub-merchants do not have their own fees configured with the platform. Instead, monetization happens through a markup applied to each charge (Payin) or payout created by sub-merchants.
Simple explanation
| Step | What happens |
|---|
| 1 | Sub-merchant processes a transaction |
| 2 | System applies the defined markup |
| 3 | Corresponding amount is automatically credited to the main merchant’s wallet |
Who can use Markup?
The Markup product is available exclusively to merchants with the markup billing model enabled on their products.
Eligibility
| Criteria | Details |
|---|
| Availability | Exclusive to merchants with markup billing model enabled |
| Applicable transactions | Only transactions created by sub-merchants |
| Not applicable | Charges or payouts created directly by the main merchant |
Ideal for companies that:
- Provide payment infrastructure to partners
- Want to scale their monetization model efficiently
- Operate with franchises, affiliates, or sub-partners
- Need separate revenue streams for parent company and sub-entities
How Markup can be applied
The product supports two ways of applying revenue, offering both flexibility and predictability.
1. Global Markup (Default)
A standard rule configured at the main merchant level.
| Aspect | Description |
|---|
| When applied | Whenever a transaction is created by a sub-merchant and no specific markup value is provided |
| Behavior | System automatically applies the global markup |
| Use case | Baseline monetization rule – ensures all transactions generate revenue |
Simple explanation
| Step | What happens |
|---|
| 1 | Sub-merchant processes a transaction |
| 2 | System applies the defined markup |
| 3 | Corresponding amount is automatically credited to the main merchant’s wallet |
Who can use Markup?
The Markup product is available exclusively to merchants with the markup billing model enabled on their products.
Eligibility
| Criteria | Details |
|---|
| Availability | Exclusive to merchants with markup billing model enabled |
| Applicable transactions | Only transactions created by sub-merchants |
| Not applicable | Charges or payouts created directly by the main merchant |
Ideal for companies that:
- Provide payment infrastructure to partners
- Want to scale their monetization model efficiently
- Operate with franchises, affiliates, or sub-partners
- Need separate revenue streams for parent company and sub-entities
How Markup can be applied
The product supports two ways of applying revenue, offering both flexibility and predictability.
1. Global Markup (Default)
A standard rule configured at the main merchant level.
| Aspect | Description |
|---|
| When applied | Whenever a transaction is created by a sub-merchant and no specific markup value is provided |
| Behavior | System automatically applies the global markup |
| Use case | Baseline monetization rule – ensures all transactions generate revenue |
2. Inline Markup2. Inline Markup
Sent directly when creating a charge or payoutSent directly when creating a charge or payout.
| Aspect | Description |
|---|
| When applied | Merchant defines exact markup amount for a specific transactionMerchant defines exact markup amount for a specific transaction |
| FormatFormat | Percentage-based or fixed amountPercentage-based or fixed amount |
| Use case | Special negotiations, campaigns, specific rules by product, region, or partnerSpecial negotiations, campaigns, specific rules by product, region, or partner |
| Priority | Always overrides the global markup for that transaction |
| Priority | Always overrides the global markup for that transaction |
Global vs. Inline Markup comparisonGlobal vs. Inline Markup comparison
| Feature | Global Markup | Inline Markup |
|---|
| Configuration level | Main merchant (default rule) | Per transaction |
| Flexibility | Fixed baseline | Highly flexible |
| Override behavior | Used when no inline is provided | Overrides global markup |
| Best for | Standard, recurring transactions | Special campaigns, negotiated deals |
| Format | Percentage or fixed | Percentage or fixed |
How to configurate?
In your Portal you’ll go to the section “MarkUp” inside “Account”, there, you will chose your account and setup the Global Markup.
What happens financially?
After a sub-merchant’s transaction is settled, the system automatically performs the financial allocation:
Financial flow
| Step | Effect |
|---|
| Markup amount deducted | From the sub-merchant |
| Markup amount credited | To the main merchant’s wallet |
| WEpayments operational fee | Charged only to the main merchant |
How it appears in statements
| Statement type | How markup appears |
|---|
| Sub-merchant statement | Separate line identified as “Markup” (debit) |
| Main merchant statement | Credit corresponding to the transaction revenue |
Example scenario
Setup
- Main merchant: Marketplace Operator
- Sub-merchant: Seller João
- Global markup: 2%
- Transaction amount: R$ 1,000
What happens
| Event | Amount | Who receives/ pays |
|---|
| Customer pays R$ 1,000 | +R$ 1,000 | Sub-merchant (gross) |
| Markup (2%) applied | -R$ 20 | Deducted from sub-merchant |
| Markup credited to main merchant | +R$ 20 | Main merchant |
| WE fee charged | -Variable | Main merchant only |
Net result
| Party | Net amount |
|---|
| Sub-merchant | R$ 980 (after markup) |
| Main merchant | R$ 20 (markup revenue) minus WE fees |
| Feature | Global Markup | Inline Markup |
|---|
| Configuration level | Main merchant (default rule) | Per transaction |
| Flexibility | Fixed baseline | Highly flexible |
| Override behavior | Used when no inline is provided | Overrides global markup |
| Best for | Standard, recurring transactions | Special campaigns, negotiated deals |
| Format | Percentage or fixed | Percentage or fixed |
Use cases
| Business model | How Markup helps |
|---|
| Franchises | Franchisor earns from franchisee transactions |
| Marketplaces | Platform earns from seller transactions |
| Payment facilitators | Facilitator earns from sub-merchant volume |
| Affiliate networks | Network owner earns from affiliate sales |
| White-label solutions | Provider earns from partner transactions |
Important notes
| Note | Details |
|---|
| Main merchant transactions | Not subject to markup (only sub-merchant transactions) |
| Inline markup priority | Always overrides global markup |
| WE fees | Charged only to main merchant |
| Sub-merchant fees | Sub-merchants have no direct fee configuration with WEpayments |