> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/grow-and-monetize/monetization/manage-buyer-credit-and-prepayment.md).

# Manage buyer credit and prepayment

Check a buyer's available credit, exposure, payment terms, and booking release rule before you qualify the buyer for a new Marketplace booking.

The Podigee Audio Video Ad Server checks buyer payment capacity before it accepts a new Marketplace booking. You can review the buyer's current exposure, approved credit, maximum exposure, payment terms, holds, and qualification state in one place.

This check protects new commitments. It does not change delivery evidence, completed delivery, or an issued invoice.

![The current One Podigee Marketplace buyer view shows buyer readiness, exposure, credit limit, eligibility, and the qualification action.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-39458b49b829a75400419ea6293b9a6fe6f8b636%2Fdoc-monetization-009-buyer-readiness.png?alt=media)

*Review exposure and eligibility before you allow a new Marketplace booking.*

## Before you start

1. Open **Monetization > Marketplace > Buyers**.
2. Confirm that you can manage Marketplace buyers.
3. Confirm the buyer's finance authority and the currency used by the credit policy.
4. Have the approved credit terms or payment instruction from your finance team.

You need Marketplace read permission to view a buyer. You need buyer credit publish permission to change a credit policy. You need Marketplace operate permission to qualify a buyer.

## Read the buyer's credit position

Open a buyer from the list. The buyer page shows:

* **Current exposure**, the open and delivered value currently assigned to the buyer.
* **Approved credit**, the maximum credit approved for the buyer.
* **Maximum exposure**, the highest combined open and delivered value the buyer may owe.
* **Available credit**, the effective limit minus current exposure. The value cannot be less than zero.
* **Payment terms**, either approved credit or prepayment required.
* **Valid until**, the end of the current credit policy.
* **Hold state**, which can stop a buyer from qualifying.

The effective limit is the lower of approved credit and maximum exposure. A buyer cannot qualify when current exposure is above this limit, even when the approved credit value is higher.

## Change credit or payment terms

Use this procedure when finance changes the buyer's limit, exposure boundary, or payment condition.

1. Open the buyer detail page.
2. Select **Change credit policy**.
3. Select the buyer's current credit position.
4. Enter the **Approved credit limit**.
5. Enter the **Maximum exposure**.
6. Select **Require prepayment for new bookings** when payment must arrive before delivery can begin.
7. Set when the new limits take effect.
8. Choose the completed finance review, or use solo confirmation when the workspace allows it.
9. Choose a booking release rule:
   * **No additional release step** when the normal limits are sufficient.
   * **Review the first booking after this limit change** when finance wants a one-time check.
   * **Review every new booking before release** when every booking needs a manual check.
   * **Require payment or finance approval** when the buyer must pay or receive finance approval before release.
10. Add a short finance note when another operator needs context.
11. Select **Save credit policy**.

Podigee saves a new policy version. It does not rewrite the earlier credit policy or the delivery history that used it.

## Qualify the buyer

The decision card shows the result that the current buyer and credit position would produce.

1. Check the predicted result.
2. Select **Check and qualify buyer**.
3. Wait for the result notice.

The result is one of these states:

* **Eligible**, the hold is clear, exposure is within the effective limit, and prepayment is not required.
* **Conditional**, the buyer can proceed after the configured prepayment or release condition is met.
* **Blocked**, a hold is active or exposure is above the effective limit.

The qualification uses the exact current buyer identity and credit policy. If either one changes, repeat the check before creating a booking.

## Use the result when you create a booking

* Create a new Marketplace booking only when the buyer is **Eligible**, or when the booking process records the required **Conditional** payment or review.
* Do not bypass a **Blocked** result. Resolve the hold or update the authorized credit policy first.
* Recheck the buyer when the booking value increases, the booking date moves, or the credit policy expires.

The qualification state controls new commitments. It does not cancel an already delivered campaign, remove its evidence, or change a past invoice.

## Recover safely

If the buyer is blocked because exposure is too high, wait for a settled payment or ask finance to approve a new limit. If the buyer is on hold, resolve the finance hold before you qualify the buyer. If the policy is expired, create a current policy and qualify again.

If the save or qualification action reports a changed version, refresh the buyer page. Review the current values again before you submit. Do not repeat a rejected action with old values.

## Expected result

The buyer has a current credit policy, a visible payment condition, and a qualification state that matches the authorized exposure and hold status. New Marketplace bookings can use the result without changing completed delivery evidence or creating a second credit decision.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.podigee.com/documentation/grow-and-monetize/monetization/manage-buyer-credit-and-prepayment.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.