> For the complete documentation index, see [llms.txt](https://adly-news.gitbook.io/adly.news-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://adly-news.gitbook.io/adly.news-docs/03-businesses/08-payments.md).

# Payments

This guide explains how payments work for businesses on [adly.news](https://adly.news), including how to pay for bookings and manage your payment history.

## Understanding Payments

### How Payments Work

When you book an ad slot:

1. **Select and configure** — Choose your ad slot and provide details
2. **Payment** — Pay securely through Stripe
3. **Confirmation** — Booking is confirmed upon successful payment
4. **Fulfillment** — Newsletter owner publishes your ad

### Payment Processing

All payments are processed through Stripe:

* Secure, encrypted transactions
* Major credit and debit cards accepted
* Payment receipts sent via email
* No card details stored on adly.news

## Making a Payment

### During Booking

When completing a booking:

1. Review your booking summary
2. Enter payment information
3. Complete the transaction

### Payment Information Required

| Field               | Description                      |
| ------------------- | -------------------------------- |
| **Card Number**     | Your credit or debit card number |
| **Expiration Date** | Month/Year                       |
| **CVC**             | 3-4 digit security code          |
| **Billing Address** | May be required                  |

### Payment Confirmation

After successful payment:

* You'll see a confirmation screen
* Email receipt is sent
* Booking status changes to "Confirmed"
* Newsletter owner is notified

## Payment Security

### Secure Processing

Stripe handles all payment processing:

* PCI-DSS compliant
* Industry-standard encryption
* Fraud detection
* Secure handling of card data

### What adly.news Stores

* Transaction history
* Payment amounts
* Invoice records

### What adly.news Doesn't Store

* Full card numbers
* CVCs
* Sensitive payment credentials

## Viewing Payment History

### Accessing Payments

1. Navigate to **Payments** in the sidebar
2. View your payment history

### Payment History Information

Your payment history shows:

| Information    | Description                          |
| -------------- | ------------------------------------ |
| **Date**       | When the payment was made            |
| **Amount**     | How much you paid                    |
| **Newsletter** | Which newsletter the payment was for |
| **Status**     | Payment status                       |
| **Booking**    | Associated booking                   |

### Payment Statuses

| Status        | Meaning                    |
| ------------- | -------------------------- |
| **Completed** | Payment successful         |
| **Pending**   | Processing in progress     |
| **Failed**    | Payment did not go through |
| **Refunded**  | Payment was refunded       |

## Invoices

### Receiving Invoices

After each payment:

* Invoice is generated
* Available in your payment history
* Email receipt sent

### Invoice Contents

Each invoice includes:

| Element            | Description               |
| ------------------ | ------------------------- |
| **Invoice Number** | Unique identifier         |
| **Date**           | Invoice date              |
| **Amount**         | Total charged             |
| **Description**    | What you paid for         |
| **Your Details**   | Your business information |

### Accessing Invoices

1. Go to **Payments**
2. Find the relevant transaction
3. Download or view the invoice

## Payment Issues

### Payment Declined

If your payment is declined:

1. Check card details are correct
2. Verify sufficient funds/credit
3. Try a different card
4. Contact your bank if issues persist

### Common Decline Reasons

| Reason             | Solution                |
| ------------------ | ----------------------- |
| Incorrect details  | Verify and re-enter     |
| Insufficient funds | Use a different card    |
| Card expired       | Update card information |
| Bank block         | Contact your bank       |
| Fraud prevention   | Verify with your bank   |

### Retry Payment

If payment fails during booking:

1. The booking may be saved as pending
2. Return to complete payment
3. Use updated or different payment method

## Refunds

### When Refunds Apply

Refunds may be issued for:

* Cancelled bookings (per platform policy)
* Non-delivery of services
* Platform errors

### Refund Process

If a refund is due:

1. Refund is initiated through the platform
2. Funds return to original payment method
3. Processing time: 5-10 business days
4. Confirmation email sent

### Refund Status

Check refund status in your payment history:

| Status                | Meaning          |
| --------------------- | ---------------- |
| **Refund Pending**    | Refund initiated |
| **Refund Processing** | In progress      |
| **Refunded**          | Complete         |

## Managing Payment Methods

### Entering Payment Information

Payment information is entered during each booking:

* No card storage required
* Enter details at checkout
* Secure one-time entry

### Saved Payment Methods

If the platform offers saved payment methods:

1. Option to save card for future use
2. Stored securely with Stripe
3. Easily select for future bookings

### Updating Payment Information

If you need to update:

* Enter new details at your next booking
* Or manage saved methods in your account settings

## Billing for Businesses

### Tax Considerations

* You're responsible for any applicable taxes
* Invoices show payment amounts
* Consult your accountant for tax treatment
* Keep records for your accounting

### Business Expense Records

Use your payment history for:

* Expense tracking
* Budget management
* Financial reporting
* Tax documentation

## Multiple Bookings

### Separate Payments

Each booking is a separate transaction:

* Pay for each booking individually
* Each has its own invoice
* Payment history shows all transactions

### Bulk Campaigns

If you have multiple bookings from a campaign:

* Each approved application is a separate booking
* Each has its own payment
* Track all in payment history

## CPL Campaign Payments

### How CPL Payments Work

CPL (Cost Per Lead) campaigns use an escrow model:

1. **Escrow on approval** — When you approve a newsletter's application, the max payout amount is charged and held in escrow
2. **Leads collected** — After the newsletter publishes your ad, leads are captured for 4 days
3. **Payout calculated** — Your actual cost is `leads × cost per lead`, capped at the max payout
4. **Funds released** — The calculated amount (minus the platform fee) is released to the newsletter owner

### Understanding CPL Costs

| Scenario     | Leads | Cost/Lead | Earned | Max Payout | You Pay       |
| ------------ | ----- | --------- | ------ | ---------- | ------------- |
| Low leads    | 10    | $10       | $100   | $500       | $100          |
| Medium leads | 40    | $10       | $400   | $500       | $400          |
| Max leads    | 60    | $10       | $600   | $500       | $500 (capped) |

> **Note:** The max payout is the most you'll ever pay for a single CPL placement, regardless of how many leads are generated.

## Common Questions

### What payment methods are accepted?

Major credit and debit cards (Visa, Mastercard, American Express) are accepted through Stripe.

### Is there a minimum booking amount?

Minimums are set by individual newsletter owners on their ad slots.

### Can I pay via invoice/wire transfer?

Currently, online card payment through Stripe is the primary method. Contact platform support for alternative arrangements.

### How long does payment processing take?

Payments are typically processed immediately. Confirmation is instant upon successful payment.

### What if I need to dispute a charge?

Contact platform support first to resolve the issue. Disputed charges may affect your account standing.

### Are payments in USD only?

Payments are processed in USD. Your bank may apply currency conversion if your card is in another currency.

### Can I get a receipt for my records?

Yes, email receipts are sent automatically, and invoices are available in your payment history.

## Best Practices

### Before Booking

* Ensure your card is valid
* Verify sufficient funds/credit
* Have billing details ready

### During Payment

* Double-check entered details
* Wait for confirmation
* Don't refresh or close during processing

### After Payment

* Save your receipt/invoice
* Verify booking confirmation
* Track in your records

## Next Steps

* View your bookings in [My Bookings](/adly.news-docs/03-businesses/05-managing-bookings.md)
* Communicate with newsletter owners via [Messages](/adly.news-docs/03-businesses/06-messages.md)
* Manage notification preferences in [Settings](/adly.news-docs/03-businesses/09-settings.md)


---

# 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://adly-news.gitbook.io/adly.news-docs/03-businesses/08-payments.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.