# Send a sale

[Charge now or authorize first](https://devportal.qa.winkpg.io/docs/decide/charge-now-or-authorize-first.md): Whether to take the money in the same request as the approval, or hold the funds and capture them when you deliver.

One request authorizes the payment and captures it, and the payment joins the merchant's next batch.

**Your answers so far**

- When do you deliver what the customer paid for? At the moment they pay.

**What to build**

Create the transaction with the Sale type. There's no second call to make and no hold to manage. If the order is canceled before the batch closes, the undo is a cancel rather than a refund, so the money never moves.

**Worth knowing**

- Captured isn't settled. The payment sits in the open batch until settlement runs, so fulfillment logic that keys on capture is deciding on a hold, not on money.
- Send an idempotency key with every create, so a retry after a timeout can't charge the customer twice.

**Where to go next**

- [Accept your first payment](https://devportal.qa.winkpg.io/docs/blueprints/accept-your-first-payment.md)
- [Transaction lifecycle and settlement](https://devportal.qa.winkpg.io/docs/guides/transaction-lifecycle-and-settlement.md)
- [Create a transaction](https://devportal.qa.winkpg.io/docs/api/transactionsCreate.md)

- [Start over](https://devportal.qa.winkpg.io/docs/decide/charge-now-or-authorize-first.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.