# Send an invoice

[Charge a customer again](https://devportal.qa.winkpg.io/docs/decide/charge-a-customer-again.md): Whether repeat payments run on a contract the platform bills, on a schedule of your own, on an invoice, or at your checkout, and what the card networks need from each.

The customer gets a numbered bill with a link to pay it, and you get a record that moves from issued to paid.

**Your answers so far**

- Is the customer there when each payment is taken? Yes. They agree to each payment as it happens.
- How does the customer pay each time? From a bill we send them.

**What to build**

Create the customer, write the invoice as a draft, and send it. Sending issues the draft, assigns its number, mints a payment link, and notifies the customer. When they pay by another route, such as a check or a bank transfer, record the payment against the invoice so it reads as paid.

**Worth knowing**

- Issuing locks an invoice. Get the line items right while it's a draft.
- Sending needs a delivery destination the merchant has configured. Check that before you rely on the platform to notify the customer.

**Where to go next**

- [Invoice a customer and get paid](https://devportal.qa.winkpg.io/docs/blueprints/invoice-a-customer-and-get-paid.md)
- [Send an invoice](https://devportal.qa.winkpg.io/docs/api/invoiceLifecycleSend.md)

- [Start over](https://devportal.qa.winkpg.io/docs/decide/charge-a-customer-again.md): go back to the first question.

## See also

- [All documentation](https://devportal.qa.winkpg.io/llms.txt): the machine-readable index of every public page on this site.