Implementation
After you define the transaction types and processing codes, configure creditor operations through Control Center, APIs, or both. Seller management is agnostic to upstream payment logic: it evaluates each merchant transaction against the creditor operation that matches its processing code and installment count, in the merchant's marketplace and creditor context.
API and Pismo Control Center configuration options
For Control Center instructions, refer to Seller management in Control Center. Contact your Pismo implementation representative if you need access or setup assistance.
For APIs, use the following endpoints to initiate creditor operations.
| Endpoint | Why it matters |
|---|---|
| Create marketplace creditor operations | Creates creditor operations in batch: one for each merchant and each installment entry in the request. |
| Update creditor operations | Updates, in batch, the creditor operations that match a filter. |
| List marketplace creditor operations | Reads back the marketplace's creditor operations, including their custom fees. |
When you create creditor operations in batch:
- The
processing_codeandstart_datevalues apply to every operation created. - A request accepts up to 1,000 merchant IDs and up to 12 installment entries.
- To change existing pricing or schedule new pricing, refer to Maintain creditor operations.
After a batch create, read the configuration back and check that each operation is present with fees populated as expected. For an example, refer to Step 3: Configure creditor operations.
Note: The Create creditor operation endpoint creates one creditor operation per request. Use processing_code. Processing codes used for merchant transactions must be reported to the Pismo setup team so it can be added to the merchant transaction filter.
Merchant transaction processing
A creditor operation remains a configuration record until Seller management receives a matching merchant transaction. There are two entry paths:
- Direct API: The Create merchant transaction endpoint creates the transaction.
- Authorization-driven: An approved payment authorization that contains the marketplace ID and merchant ID results in the merchant transaction being created, with no separate create call.
For more information, refer to Managing merchant transactions and Running Seller marketplace operations.
A transaction is processed only when its processing code and installment count match an existing creditor operation. If no operation matches, the transaction is not processed and no receivable is created. In the authorization-driven path this does not surface as an API error, so verify your configuration in advance and confirm that expected receivables appear in the receivables schedule.
For request examples, refer to Step 4: Process merchant transactions.
Updated about 4 hours ago