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.

EntityRole in the exampleID used in the samples
AcmePayCustomer defining business requirements—
Acme Retail MarketplaceMarketplace where rules are applied{marketplaceId} in request paths
ABC FurnitureMerchant generating transactionsMerchant ID 4458801
ABC Furniture Creditor AccountReceives settlement fundsCreditor ID 777

This example has eight steps:

  1. Establish business structure: Create the marketplace, the merchant, and its creditor, including advancement terms.
  2. Establish transaction classifications: Assign processing codes to AcmePay's transaction classifications.
  3. Configure creditor operations: Configure MDR tax, create the PC300 creditor operations, and verify them.
  4. Process merchant transactions: Submit a sale and a cancellation.
  5. Evaluate creditor operation: See how Seller management applies the creditor operation to the sale.
  6. Monitor and review receivables: Check the receivables schedule against the expected outcomes.
  7. Settlement processing: Confirm settlement to the creditor account.
  8. Receivables advancement: Simulate an advancement request.

Did this page help you?