Marketplace
What is Marketplace?
A marketplace is an environment where multiple sellers or service providers sell within a single platform, allowing buyers to purchase items from different stores with a single payment.
- Benefit for the consumer: centralized shopping experience.
- Benefit for sellers: expanded sales without physical infrastructure or their own marketing.
- Benefit for the marketplace: monetization via commissions and increased average order value.
Payment Splitting - BS2 Pay Concept
Splitting occurs when a customer makes a single payment and BS2 Pay automatically divides that transaction into individual payments to each seller according to rules defined by the marketplace. Splitting is exclusive to Paycore platform clients.
The following image demonstrates how this payment splitting process occurs, not the transaction splitting process:
Advantages of our Split Platform
- Split during authorization/capture.
- Multiple receivers and granular commissioning.
- Reconciliation through reports and EDI.
- Simplified onboarding via API or email.
- Split performed as a percentage or fixed amount.
Authorization/Capture (Credit/Debit Card)
To create a credit or debit card transacion, a POST request must be sent to the /v1/payments endpoint, as described on the link https://developers.adiq.io/manual/ecommerce#requisio-v1
- The 'sellers' structure must only be sent in Marketplace transactions.
- Marketplace transactions are available only for White Label Partners and Sub-acquirers integrated with Paycore.
- For debit card transactions, 3DS 2.0 authentication is mandatory.
Sellers Structure
The 'sellers' node defines the financial split between multiple establishments. Each seller receives its portion of the total amount and may include detailed items with specific values and fees.
- sellers.id - Unique identifier of the seller/sub-seller.
- sellers.amount - Total amount allocated to the seller.
- sellers.items - Item-level structure including amount, ratePercent, or rateAmount.
Enables granular splitting, commissioning, and reconciliation per seller.
Cancelation
Cancellations in marketplace transactions allow full or partial cancellation by seller, as long as they occur within the established D+N timeframes:
- Maximum of 90 days for debit.
- Maximum of 180 days for credit.
- Partial cancellation is available for marketplace transactions only by items, not by amounts.
For information on how to perform this operation, access the documentation at: https://developers.adiq.io/manual/ecommerce#cancelamento
Late Capture (Pre-authorization)
Used to capture a pre-authorization (PA to CAP). The Marketplace may send proportional split.
For information on how to perform this operation, access the documentation at: https://developers.adiq.io/manual/ecommerce#captura
Unlock (Payment Release)
The unlock process releases amounts retained in Paycore's receivables schedule. It is used when there is a delivery trigger, inventory control, or any other condition defined by the marketplace, for example.
That is, the unlock represents the authorization to release payment from the receivables schedule within the PAYCORE platform.
Request
{
"sellerId": "901",
"amount": 690,
"date": "2019-11-13T13:48:18.4361271+00:00",
"item": {
"id": "P115DU90",
"amount": 690
}
}
| Property | Description | Type | Location | Mandatory |
|---|---|---|---|---|
PaymentId | Identifier of the payment to be consulted. | string | path | yes |
SellerId | Identifier of the business. | string | body | yes |
Amount | Total unblocking amount (in cents). | integer | body | yes |
Date | Date the payment was unblocked. | datetime | body | yes |
Item.Id | Identifier of the item. | string | body | yes |
Item.Amount | Amount of the item (in cents). | integer | body | yes |
Response
Success Status code 200Bad Request Status code 400
[
{
"tag": "PaymentId",
"description": "Não pode ser nulo ou vazio."
}
]
Update Unlocked Payment
To update the payment release date for a transaction made via Marketplace, you must send a request using the PUT method to the resource as shown in the example.
Request
{
"sellerId": "901",
"amount": 690,
"date": "2019-11-13T13:48:18.5180698+00:00",
"previousDate": "2019-11-13T13:48:18.5180765+00:00",
"item": {
"id": "P115DU90",
"amount": 345
}
}
| Property | Description | Type | Location | Mandatory |
|---|---|---|---|---|
PaymentId | Identifier of the payment to be consulted. | string | path | yes |
SellerId | Identifier of the business. | string | body | yes |
Amount | Total unblocking amount (in cents). | integer | body | yes |
Date | Date the payment was unblocked. | datetime | body | yes |
PreviousDate | Date previously informed. | datetime | body | yes |
Item.Id | Identifier of the item. | string | body | yes |
Item.Amount | Amount of the item (in cents). | integer | body | yes |
Response
Success Status code 200Bad Request Status code 400
[
{
"tag": "PaymentId",
"description": "Não pode ser nulo ou vazio."
}
]
Example of settlement and amounts

Settlement Triggers
- The Marketplace authorizes BS2 Pay to settle according to its own rules.
- The trigger is based on the item.
- Settlement with the Marketplace may or may not be linked to the trigger.
Flexible Settlement Terms
- The Marketplace may define D+10 for Merchant 1, D+15 for Merchant 2, and so on.
- The Marketplace's commission will follow each store's plan.