Suggestion: Add authorization code to the Charge object

[Felix Kenton]

Suggestion

I'd like to suggest adding an "authorization code" field to a Charge object, which would enable us to speed up the return of funds when cancelling an un-captured Charge.

Background

We use an auth-and-capture system, where a payment is authorised ahead of it being captured. In some situations we are required to cancel one of these authorisations (which we can already do using Stripe) however the reserved funds often take a number of days to become available to the customer again.

Sometimes a customer will ask us to speed up this process in any way possible, as they urgently need access to the funds. With the UK's banking system, it seems that the funds can usually be made available within hours by sending a fax containing what is called an "authorisation code" to the customer's bank.

There doesn't currently appear to be a way of obtaining this code through Stripe, but some customers have been able to obtain this code directly from their bank for us and have had their funds returned promptly. Other banks refuse to provide this code the customer, as it is something that is supposed to be held by the merchant as a part of proving that they initiated the authorisation. Through Stripe, this information is not available to merchants, which leaves us unable to help customers of these banks.

-

Presumably these authorisation codes are all held by Stripe anyway, so implementation would be easy. I'd love to get feedback on the feasibility of this suggestion and whether there are any downsides to this change that I'm unaware of.

Cheers,

Felix

[Jason Troy]

+1 ... FWIW, Some customers appreciate the Auth code printed on the receipt to give them that warm reassuring feeling. haha

--
You received this message because you are subscribed to the Google Groups "Stripe API Discussion" group.
To post to this group, send email to api-d...@lists.stripe.com.
Visit this group at http://groups.google.com/a/lists.stripe.com/group/api-discuss/.

To unsubscribe from this group and stop receiving emails from it, send an email to api-discuss...@lists.stripe.com.

[Ben Sebborn]

+1

This message may contain privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient you are hereby notified that any use, dissemination, distribution, disclosure or reproduction of this message is strictly prohibited. If you receive this message in error please notify Skiddle Ltd immediately. Whilst Skiddle Ltd operates antivirus software it does not accept responsibility for any damage whatsoever or howsoever that is caused by viruses or infections being passed on. Any views expressed within this message are solely those of the sender and do not necessarily reflect the views of Skiddle Ltd.