Card management API | Hacker News Reader

Card management API

stripe.com

83 pointsgdb17 comments

I swear that Stripe is monitoring my private repo. It's like they know exactly what kind of hacky workaround I just implemented on my project and wrote something to support it in an elegant way.

First ACH, and now this. Nice work, again, Stripe.

Go Stripe! Now if you could just start support USD payments for UK merchants (without a US bank account) you'd make me really super happy. Integrating Stripe is a pleasure and if I never have to deal with PayPal ever again that would be nice :)

We're going to add support for this.

That's awesome to hear! I have had to fall back to PayPal for our new US store. Loving the Stripe UK beta!

This is right on time. Currently working on a site that makes use of multiple cards per customer. Great job, once again, Stripe!

Wow. This definitely changes things a lot. Businesses can now store credit cards safely without ever having to worry about PCI compliance. That saves a lot of time and money!

This brings a lot more clarity to the API update a few days ago. The API update was a bit more cryptic being only a short description of the change.

By far our most desired feature right now is to allow a single customer to have more than one subscription. It's crazy what we go through right now to allow people to have two or more recurring products on the same account. :-)

Yep, we're working on this as well! :)

It sounds like the single default_card is used for recurring payments, and other saved cards are used for one-offs. No separate card subscriptions yet. Is that right?

You can use your default card for once-off charges as well (just don't specify a card ID when making a charge with a customer).

You're right that you can't use a separate card for subscriptions yet -- we just use the customer's default card. We'd love to hear your feedback on this though (feel free to ping me at amber@stripe.com)!

It'd be handy to let a customer have multiple subscriptions, and to have those subscriptions be associated with one of the customer's cards.

Currently that has to be abstracted away on client-side databases and we end up having multiple 'Stripe customers' associated with a single client, so it fudges our customer count in the Stripe management interface.

Makes sense.

What would the ideal behavior be if your customer updates their default card? Should the recurring billing continue chugging along with the card it was created with, or use the new card instead?

I would expect to be able to list subscriptions and list what card is associated with each. I would show an "Update Card" button next to each subscription. That button would prompt the user to either choose from a list of stored cards or add a new one.

The concept of a "default" card would come up when creating a new subscription or charge, and would be presented as the default selected payment option. The user would be able to select another card or add a new one.

I'm thinking of something similar to Amazon's checkout credit card selection screen.

Newegg and other websites keep a history of cards you've used, so this new 'multiple cards' feature brings Stripe closer to feature parity with most closed systems. It's really impressive that Stripe offers these features openly to the world.

Most major websites that have check-outs operate similarly to how you describe, but there's no 'default' card presented at check-out -- instead it displays the last card used for the last purchase.

I'd say with almost absolute certainty the recurring billing should continue to charge the card it was created with. default_card should essentially be a pointer to a customer's preferred card.

YES!!!!

Reply on news.ycombinator.com