# Use Cases
source: https://developer.mastercard.com/payment-acceptance-api/documentation/use-cases/index.md

This section outlines the key functional capabilities available to Creditor Agents through the Payment Acceptance API. These use cases support the complete operational lifecycle of card‑based B2B payments, allowing Creditor Agents to onboard Creditors, manage payment configurations, monitor transaction statuses, and retrieve Debtor information.

## Payment Acceptance API Requests {#payment-acceptance-api-requests}

The Payment Acceptance API supports seven API request types:

|               Use Case               |                                                                                                                               Description                                                                                                                                |
|--------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Creditor Agent Webhook Notifications | Sends webhook notifications to Creditor Agents when Debtor Agents submit payment instructions in Mastercard Commercial Direct Payments (CDP). [Learn more](https://developer.mastercard.com/payment-acceptance-api/documentation/use-cases/event-notifications/index.md) |
| Card Payment Status Update           | Updates an existing card payment instruction for cancellation. [Learn more](https://developer.mastercard.com/payment-acceptance-api/documentation/use-cases/card-payment-status-update/index.md)                                                                         |
| Card Payment Status Inquiry          | Retrieves the current status of a submitted card payment instruction. [Learn more](https://developer.mastercard.com/payment-acceptance-api/documentation/use-cases/card-payment-status-inquiry/index.md)                                                                 |
| Register a Creditor                  | Registers and validates creditor details to enable secure CDP workflows. Registered information can be retrieved for verification or updates. [Learn more](https://developer.mastercard.com/payment-acceptance-api/documentation/use-cases/register-creditor/index.md)   |
| Creditor Profiles                    | Maintains creditor payment profiles by enabling updates or complete removal of existing records. [Learn more](https://developer.mastercard.com/payment-acceptance-api/documentation/use-cases/creditor-profiles/index.md)                                                |
| Creditor Payment Controls            | Enables Creditor Agents to define and manage payment preferences on behalf of their Creditors. [Learn more](https://developer.mastercard.com/payment-acceptance-api/documentation/use-cases/creditor-payment-controls/index.md)                                          |
| Retrieve Debtor Details              | Retrieves debtor information to support payment processing, routing, and reconciliation. [Learn more](https://developer.mastercard.com/payment-acceptance-api/documentation/use-cases/retrieve-debtor-details/index.md)                                                  |

## End‑to‑end Commercial Card Payment Process {#endtoend-commercial-card-payment-process}

Diagram paymentinitiation

1. The Debtor Agent initiates the card payment request to the CDP.
2. CDP validates the request.
3. CDP sends APPROVED, DECLINED, or REJECTED status to the Debtor Agent.

#### Scenario 1: Creditor set up to pay through a Creditor Agent {#scenario-1-creditor-set-up-to-pay-through-a-creditor-agent}

4. CDP sends payment initiation notification to the Creditor Agent.
5. The Creditor Agent sends an acknowledgment of payment notification to CDP.
6. CDP sends a **SUBMITTED** payment status notification to the Debtor Agent.
7. Creditor Agent sends an authorization status; APPROVED, DECLINED, or REJECTED to CDP.
8. CDP forwards the authorization status to the Debtor Agent.
9. The Creditor Agent delivers reconciliation data to the Creditor.
10. The Creditor Agent sends a SETTLED reconciliation status to CDP.
11. CDP forwards the SETTLED status to the Debtor Agent.

#### Scenario 2: Creditor set up to pay through Mastercard Gateway (MPGS) {#scenario-2-creditor-set-up-to-pay-through-mastercard-gateway-mpgs}

12. CDP sends the card payment request to Mastercard Gateway (MPGS).
13. MPGS sends an acknowledgment of the payment to CDP.
14. CDP sends a **SUBMITTED** payment status notification to the Debtor Agent.
15. MPGS sends an APPROVED, DECLINED, or REJECTED status back to CDP.
16. CDP forwards the status to the Debtor Agent.
17. For **APPROVED** payments, CDP delivers remittance data to the Creditor (if requested).

#### Scenario 3: Email payment when the Creditor is not registered with the CDP {#scenario-3-email-payment-when-the-creditor-is-not-registered-with-the-cdp}

18. CDP sends the card payment request payload and remittance data through the Mastercard email service.
19. The email service sends an acknowledgment to CDP.
20. CDP delivers a secure email containing the payment request and remittance data to the Creditor.
21. CDP sends a **SUBMITTED** payment status notification to the Debtor Agent.
22. CDP captures the payment status for Mastercard‑generated virtual cards.
23. CDP sends the payment status for Mastercard‑generated virtual cards to the Debtor Agent.

Note: For non‑Mastercard‑branded cards and real cards used in email delivery, payment status updates are not returned.

## Error Handling {#error-handling}

To see information about possible errors that can be returned from the service, refer to the [Codes and Formats](https://developer.mastercard.com/payment-acceptance-api/documentation/code-and-formats/index.md) page.

## Next Steps {#next-steps}

Now that you have an understanding of the different use cases the service uses, proceed to the [API Reference](https://developer.mastercard.com/payment-acceptance-api/documentation/api-reference/index.md) section to interact with all of our endpoints on the API explorer.