# Ringup

> Identity and payments for voice agents

## Docs

- [Charge the saved card](https://docs.ringup.dev/api-reference/charge-the-saved-card.md): Charge the caller's saved card, off-session, settling to the merchant's own payment processor. Only after the caller verbally agrees. Idempotent per call id and amount: retries return the original payment.
- [Check payment completion](https://docs.ringup.dev/api-reference/check-payment-completion.md): Whether the caller has completed payment, for example after send_link while the call is still going.
- [Get the payment policy for this purchase](https://docs.ringup.dev/api-reference/get-the-payment-policy-for-this-purchase.md): Ask Ringup how payment should be handled for this purchase, before taking payment. Resolved per purchase from the merchant's settings and the amount: the same merchant can return different statuses for different orders.
- [Introduction](https://docs.ringup.dev/api-reference/introduction.md): Five REST tools for platforms that own their whole conversation flow.
- [Look up the caller](https://docs.ringup.dev/api-reference/look-up-the-caller.md): Whether the caller has a saved card with Ringup, resolved from the caller number header. Call this as soon as the payment step begins; never mention a card on file before this confirms one.
- [Text the caller a pay link](https://docs.ringup.dev/api-reference/text-the-caller-a-pay-link.md): Text the caller a secure pay link: first-time callers, or a caller who wants a different card. Only after the caller clearly says yes to the text. Card entry happens on a Ringup-hosted page; the number never touches the call.
- [How it works](https://docs.ringup.dev/concepts/how-it-works.md): Your agent always hands off the same way; Ringup decides what happens next.
- [Caller and merchant identity](https://docs.ringup.dev/concepts/identity.md): Both identities are resolved server-side from call context. The model never types either one.
- [Payment policy](https://docs.ringup.dev/concepts/payment-policy.md): Whether payment is required, optional, or absent is a merchant setting Ringup serves per purchase.
- [Testing](https://docs.ringup.dev/concepts/testing.md): A shared sandbox with ready-made merchants and callers. Test mode works before you configure anything.
- [What is Ringup](https://docs.ringup.dev/index.md): Identity and payments for voice agents. Returning callers are recognized by phone number and pay with their saved card in one sentence.
- [Vapi](https://docs.ringup.dev/integrations/vapi.md): Add payments to an existing Vapi agent or squad: provision, rehearse on a private line, go live, roll back.
- [Quickstart](https://docs.ringup.dev/quickstart.md): Talk to a working payments demo in about a minute, then take your own agent live.

## OpenAPI Specs

- [openapi](https://docs.ringup.dev/api-reference/openapi.json)