Live data from Hacker News

Stripe Integration for Twilio Pay

stripe.com

1–10 of 32 posts

Re: Stripe Integration for Twilio Pay

#3
This looks pretty cool. I keep coming up with Twilio-based side projects I want to build, but the abuse potential keeps me from actually releasing anything useful. With this, maybe I can charge users $.0X per call minute, or $X/month to recoup my Twilio costs.

Re: Stripe Integration for Twilio Pay

#4
It’s not 100% clear from the documentation but it appears the card details have to be keyed in and there’s no voice recognition mode.

It would be great to hear a demo of what sounds like, particularly the error handling.

I absolutely get the benefit of insulating your agents from the billing data. Not so keen on an abrupt switch to touch-tone inputs during a call though.

Re: Stripe Integration for Twilio Pay

#5
I worked on a very similar product a few years ago. There were a few companies battling over patent rights for similar implementations of DTMF tone suppression in the payment space.

Not sure what happened with that but looks like essentially the same idea here. Always thought it was pretty niche now everyone has a browser in their pocket.

Re: Stripe Integration for Twilio Pay

#6
post #3

This looks pretty cool. I keep coming up with Twilio-based side projects I want to build, but the abuse potential keeps me from actually releasing anything useful. With this, maybe I can charge users $.0X per call minute, or $X/month to recoup my Twilio costs.

> the abuse potential

It's kinda hard to abuse recently. You can do heavy geo locking in order to not get fucked over by abuse to other countries.

Re: Stripe Integration for Twilio Pay

#7
post #5

I worked on a very similar product a few years ago. There were a few companies battling over patent rights for similar implementations of DTMF tone suppression in the payment space. Not sure what happened with that but looks like essentially the same idea here. Always thought it was pretty niche now everyone has a browser in their pocket.

Interestingly, this might be in response to the new PCI requirements.

In the past, if you iframe'd a payment processor site, you didn't need to be PCI compliant while the new spec requires everyone who is involved in the process to be compliant.

I wonder if this will be the future of payment processing, just outsourcing to Twilio and Stripe.

Re: Stripe Integration for Twilio Pay

#8
post #5

I worked on a very similar product a few years ago. There were a few companies battling over patent rights for similar implementations of DTMF tone suppression in the payment space. Not sure what happened with that but looks like essentially the same idea here. Always thought it was pretty niche now everyone has a browser in their pocket.

Interestingly, this might be in response to the new PCI requirements. In the past, if you iframe'd a payment processor site, you didn't need to be PCI compliant while the new spec requires everyone who is involved in the process to be compliant. I wonder if this will be the future of payment processing, just outsourcing to Twilio and Stripe.

TIL, they should be geared up to take advantage then. We had PCI compliancy but like you mention the big players will take most of the pie.

Re: Stripe Integration for Twilio Pay

#9
post #4

It’s not 100% clear from the documentation but it appears the card details have to be keyed in and there’s no voice recognition mode. It would be great to hear a demo of what sounds like, particularly the error handling. I absolutely get the benefit of insulating your agents from the billing data. Not so keen on an abrupt switch to touch-tone inputs during a call though.

From the linked post: "when it’s time to collect the payment, the agent activates Twilio to let the customer enter payment info using their keypad—agents can follow the customer’s progress, but won’t see or hear the card details."

Re: Stripe Integration for Twilio Pay

#10
post #3

This looks pretty cool. I keep coming up with Twilio-based side projects I want to build, but the abuse potential keeps me from actually releasing anything useful. With this, maybe I can charge users $.0X per call minute, or $X/month to recoup my Twilio costs.

> the abuse potential It's kinda hard to abuse recently. You can do heavy geo locking in order to not get fucked over by abuse to other countries.

Do you have to do it yourself or Twilio takes care of that?
Post reply on HN