Skip to main content
When a caller has no saved card, or a recognized caller wants to use a different one, there is nothing to charge yet. send_link texts them a secure pay link so they can pay on their own phone, without ever reading a card number aloud on the call. 
curl -X POST https://ringup.dev/api/tools/send_link \
  -H "Content-Type: application/json" \
  -H "X-Caller-Number: +14155550142" \
  -H "X-Ringup-Merchant: tonys-pizza" \
  -d '{ "amount_cents": 1900 }'
Response
{ "ok": true, "sent_to": "+14155550142", "link": "https://ringup.dev/pay" }

​
What happens

The caller taps the link and pays on a Ringup-hosted page. The card number is entered there, on a web page, so it never touches the call. Once the payment clears, the card is saved by phone number, so the same person is recognized on their next call, at any Ringup merchant, and can pay from a saved card with no link at all. Only send the link after the caller clearly agrees to the text.

​
During the call or after

Payment can complete either way:
  • During the call. The caller pays while still on the phone. You can poll the payment state so your agent knows the moment it clears and can close the call knowing the order is paid.
  • After the call ends. The caller hangs up and pays later from the same link. The call does not have to wait.
Either way, the caller gets an SMS receipt, and your server learns the outcome from a checkout.completed webhook with method: "link". A link payment is not a separate event: it is a checkout.completed like any other, so one webhook handler covers both a saved-card charge and a first-time link payment. Once the caller has paid once, prefer a direct charge on their saved card next time.

​
Next steps

Charge

The recognized-caller path: run a saved card without a link.

Webhooks

A first-time link payment lands as checkout.completed too.