The call creates a Stripe customer, and your team sends the link
No card number is spoken on a GreetKeeper call. Our webhook feeds a Zap, on a paid Zapier plan, that prepares the customer record so billing is one click afterwards.
Caller
“I'd like to book the intro session. Happy to pay upfront if you send me something. Email is on my last message.”
What happened next
- Session booked and the caller's email captured on the call
- Zapier created a Stripe customer with that email and the caller's name
- Owner sent the payment link from Stripe the same evening
How GreetKeeper connects to Stripe
Three states, and we publish the one that is true rather than the one that reads best.
| Tool | How it connects | What that means |
|---|---|---|
| Stripe | Through Zapier |
What Stripe is and what Zapier reaches
Stripe is payment infrastructure. It holds customers, subscriptions, invoices and the card details people enter on a checkout page that Stripe itself hosts.
The hosting part is the whole security model. Card numbers go straight from the payer's browser to Stripe. Your systems never see them, and that is why Stripe works the way it does.
Stripe's Zapier app can create a customer, find one, and trigger on events like a successful payment. Those are the actions worth using after a phone call.
What the Zap writes
A customer object in Stripe, with the details the caller gave and nothing else.
Name, email and phone number go onto the customer. The summary of what they wanted can go into the description or metadata, so whoever invoices knows what the charge is for.
From there your team sends a payment link or an invoice from Stripe. The payer enters their own card on Stripe's page. That is the only place a card should ever be typed.
You can also run the flow the other way. A successful payment in Stripe triggers its own Zap, which can post to your team or update a record. That side has nothing to do with the phone call.
Setting it up
Use test mode first. A live key and a wrong mapping is an unpleasant combination.
Catch the webhook, then connect Stripe with test mode keys
Webhooks by Zapier with Catch Hook is the first step, listening at an address you paste into GreetKeeper. Connect Stripe after it. Build and verify the whole flow against test mode. Switch the connection to live only once you have seen a correct customer object appear.
Search Stripe for an existing customer by email
Email is the reliable key here. Phone numbers arrive in different formats and will not match cleanly. Allow the search to miss without failing the Zap.
Create the customer when no match is found
Map name, email and phone. Put the call id and the reason for calling in metadata rather than the name field. Metadata is searchable in Stripe and keeps the customer list readable.
Decide who sends the link, and write it down
The Zap stops at the customer record. Someone has to send the payment link. Name that person in your process notes, or callers wait for an email nobody sent.
The hard boundary
Questions about Stripe and GreetKeeper
Can a caller pay during the call?
No. GreetKeeper does not capture card details on a call. The caller gets a Stripe payment link afterwards and pays on Stripe's hosted page.
What if the caller gives no email?
You cannot create a useful Stripe customer without one, so the Zap should filter those out. Your team follows up by phone and collects the email then.
Can I match a payment back to the call it came from?
Put the call id from the webhook in the customer metadata when you create it. Later payments carry that customer, so you can trace a charge back to the conversation that started it.
Is Stripe's Zapier app all we pay Zapier for?
You pay Zapier for a plan, not per app, and it has to be a paid one. The Zap receives GreetKeeper's webhook through Webhooks by Zapier, which is premium. We have no Zapier app yet.
See the customer object appear
We will run it in test mode. Two minutes.