Skip to main content
POST
Create Payin with Inline Markup

Create Payin with Inline Markup

When creating a payin charge, you can include an inline markup object in the request payload.
Inline markup takes precedence: If you send a markup object in the charge creation request, it will override any global or submerchant markup configurations.

Markup Object Structure

The markup object should be added to the request body when creating a charge via POST /v2/payin/payments.
object
Optional inline markup configuration for this specific charge.
When mode is fixed, do not send min_charge_value or max_charge_value.

Request Examples

Response

integer
WEpayment’s auto generated id, use this id to perform conciliation or perform queries via API / Dashboard.
object
Merchant object.
string
WEpayments auto generated hash, use this hash to send your user to the payment page.
string
The WEpayments payment page is the place where you will redirect the end customer to pay the bill.
string
Your identification number.
string
Payment method that will be used in payin.Values: pix, boleto
integer
The payin total amount in cents.
object
Currency object.
string
Current status of the payin.Example: pending
object
Inline markup configuration applied to this charge.

How It Works

  1. Priority: The inline markup configuration takes precedence over global and submerchant markup settings.
  2. Calculation (for percent mode):
    • The system converts the markup amount to percentage: amount * 100 = percentage%
    • Then calculates: transaction_amount * (amount)
    • If calculated value < min_charge_value → applies min_charge_value
    • If calculated value > max_charge_value → applies max_charge_value
    • Otherwise → applies the calculated value
  3. Fixed Mode: When using fixed mode, the markup amount is applied directly regardless of the transaction value.

Create Charge

Complete documentation for creating payin charges

About Markup

Learn about markup types and configuration levels