<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>subsubsub</author><text>As a previous commenter mentioned Revolut do this.&lt;p&gt;However I would suggest a temporary card that only lasts for 2 transactions.&lt;p&gt;- the authorization charge (e.g. $1 on amazon.com) [1]&lt;p&gt;- the actual amount of the purchase&lt;p&gt;Too many times I have been caught out by the authorization charge, only to have the actual purchase fail.&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;aws.amazon.com&amp;#x2F;premiumsupport&amp;#x2F;knowledge-center&amp;#x2F;aws-authorization-charges&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;aws.amazon.com&amp;#x2F;premiumsupport&amp;#x2F;knowledge-center&amp;#x2F;aws-a...&lt;/a&gt;</text><parent_chain><item><author>ryandrake</author><text>As a credit card customer it would be nice to be able to generate one or more temporary cards (physical or not), which are authorized for one transaction only, but are otherwise identical to my main card. That way I can use it with a merchant I simply don’t trust to have their act together, then safely toss it in the trash.</text></item><item><author>lachyg</author><text>(I work on Stripe Issuing.)&lt;p&gt;We&amp;#x27;ve been primarily focused to date on companies where issuing cards is core to providing their business to customers, for example a startup that provides expensing customers, or a platform that needs to purchase goods in the real world. We&amp;#x27;re less focused on a business just using it for their own expensing (as we don&amp;#x27;t have receipt upload functionality, etc).&lt;p&gt;To your two other questions though:&lt;p&gt;(1) Could users approve things in real time? Sort of. We provide the ability (as you noticed) through API, but it needs to be responded to in &amp;lt; 2s, which means it&amp;#x27;s not possible for a human to be in the flow.&lt;p&gt;(2) Could this be linked to an external bank account? Again, sort of. To get in the weeds: as soon as we approve an authorization, we&amp;#x27;re on the hook for those funds. A debit to an external balance (or bank account) may fail and Stripe would be on the line. This is why we typically require funds to be in a Stripe account prior to purchases taking place.</text></item><item><author>TheTaytay</author><text>This is really impressive, like the rest of the Stripe API! Although many people here are asking about creating virtual banks and issuing cards to customers, it appears that the intended audience of this API is a business that has a Stripe account, that wants to be able to issue cards to employees&amp;#x2F;trusted officials that charge against that single Stripe account. There is no mention of issuing cards to external customers that link against their own, external accounts, right?&lt;p&gt;I ask because the webhook that Stripe fires at purchase time is fantastic, and you could build some great things if their API gave you access to authorized real-time purchase data for customers. This doesn&amp;#x27;t appear to facilitate that though.&lt;p&gt;Does anyone know of an API that would allow a Credit Card user the ability to grant real-time webhooks to a 3rd party as they swipe their card? The closest I&amp;#x27;ve ever found would be setting up spending email spending alerts (that certain banks allow), and then forwarding the emails to said 3rd party. It&amp;#x27;s clunky, and would only work with a few banks. Something like this issuing API would work if Stripe allowed you to issue a card that was linked to a customer&amp;#x27;s  existing card&amp;#x2F;account. They&amp;#x27;d basically be saying, &amp;quot;If I swipe _this_ card that you sent me, I&amp;#x27;m agreeing to let you get notified.&amp;quot; The other way I&amp;#x27;ve considered would involve creating your own bank and issuing your own cards, but that&amp;#x27;s real work on both the developer and the customer&amp;#x27;s part :)</text></item></parent_chain></comment><story><title>Stripe Issuing – An API for creating physical and virtual cards</title><url>https://stripe.com/issuing</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>akeating</author><text>I&amp;#x27;ve been watching Revolut who introduced something like this a while back &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;blog.revolut.com&amp;#x2F;introducing-disposable-virtual-cards&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;blog.revolut.com&amp;#x2F;introducing-disposable-virtual-card...&lt;/a&gt;</text><parent_chain><item><author>ryandrake</author><text>As a credit card customer it would be nice to be able to generate one or more temporary cards (physical or not), which are authorized for one transaction only, but are otherwise identical to my main card. That way I can use it with a merchant I simply don’t trust to have their act together, then safely toss it in the trash.</text></item><item><author>lachyg</author><text>(I work on Stripe Issuing.)&lt;p&gt;We&amp;#x27;ve been primarily focused to date on companies where issuing cards is core to providing their business to customers, for example a startup that provides expensing customers, or a platform that needs to purchase goods in the real world. We&amp;#x27;re less focused on a business just using it for their own expensing (as we don&amp;#x27;t have receipt upload functionality, etc).&lt;p&gt;To your two other questions though:&lt;p&gt;(1) Could users approve things in real time? Sort of. We provide the ability (as you noticed) through API, but it needs to be responded to in &amp;lt; 2s, which means it&amp;#x27;s not possible for a human to be in the flow.&lt;p&gt;(2) Could this be linked to an external bank account? Again, sort of. To get in the weeds: as soon as we approve an authorization, we&amp;#x27;re on the hook for those funds. A debit to an external balance (or bank account) may fail and Stripe would be on the line. This is why we typically require funds to be in a Stripe account prior to purchases taking place.</text></item><item><author>TheTaytay</author><text>This is really impressive, like the rest of the Stripe API! Although many people here are asking about creating virtual banks and issuing cards to customers, it appears that the intended audience of this API is a business that has a Stripe account, that wants to be able to issue cards to employees&amp;#x2F;trusted officials that charge against that single Stripe account. There is no mention of issuing cards to external customers that link against their own, external accounts, right?&lt;p&gt;I ask because the webhook that Stripe fires at purchase time is fantastic, and you could build some great things if their API gave you access to authorized real-time purchase data for customers. This doesn&amp;#x27;t appear to facilitate that though.&lt;p&gt;Does anyone know of an API that would allow a Credit Card user the ability to grant real-time webhooks to a 3rd party as they swipe their card? The closest I&amp;#x27;ve ever found would be setting up spending email spending alerts (that certain banks allow), and then forwarding the emails to said 3rd party. It&amp;#x27;s clunky, and would only work with a few banks. Something like this issuing API would work if Stripe allowed you to issue a card that was linked to a customer&amp;#x27;s  existing card&amp;#x2F;account. They&amp;#x27;d basically be saying, &amp;quot;If I swipe _this_ card that you sent me, I&amp;#x27;m agreeing to let you get notified.&amp;quot; The other way I&amp;#x27;ve considered would involve creating your own bank and issuing your own cards, but that&amp;#x27;s real work on both the developer and the customer&amp;#x27;s part :)</text></item></parent_chain></comment><story><title>Stripe Issuing – An API for creating physical and virtual cards</title><url>https://stripe.com/issuing</url></story>