Creditor operations end-to-end
This example follows a hypothetical customer, AcmePay, through the creditor operations lifecycle: setting up its business structure, classifying transactions, configuring creditor operations, processing transactions, and then monitoring, settlement, and optional receivables advancement. As the example progresses, AcmePay completes the planning matrix as a living implementation record.
AcmePay creditor operations
AcmePay operates a retail marketplace whose merchants accept several payment methods and payment conditions. The example follows one merchant, ABC Furniture, and one transaction scenario.
| Entity | Role in the example | ID used in the samples |
|---|---|---|
| AcmePay | Customer defining business requirements | — |
| Acme Retail Marketplace | Marketplace where rules are applied | {marketplaceId} in request paths |
| ABC Furniture | Merchant generating transactions | Merchant ID 4458801 |
| ABC Furniture Creditor Account | Receives settlement funds | Creditor ID 777 |
This example has eight steps:
- Establish business structure: Create the marketplace, the merchant, and its creditor, including advancement terms.
- Establish transaction classifications: Assign processing codes to AcmePay's transaction classifications.
- Configure creditor operations: Configure MDR tax, create the PC300 creditor operations, and verify them.
- Process merchant transactions: Submit a sale and a cancellation.
- Evaluate creditor operation: See how Seller management applies the creditor operation to the sale.
- Monitor and review receivables: Check the receivables schedule against the expected outcomes.
- Settlement processing: Confirm settlement to the creditor account.
- Receivables advancement: Simulate an advancement request.
Updated 2 days ago
What’s Next
Did this page help you?