RequestOptions missing ClientSecret properties

[alessandroghizzardi]

I've read in the documentation che Stripe.NET is intended to be used client side, and so any source retrieved with SourceService.Get method should have the private key provided. Calling a Source using the public key and source id returns a "missing client secret" error.
This behaviour doesn't consider the use of Stripe.NET in Xamarin as a client side library for Stripe enabled mobile application. Here we need to use Public key to tokenize a credit card, and use a 3D Secure source to check if it's available. We cannot retrieve back the 3D Secure source to check if the authorization has been provided or not. Right now we switched back to the REST API that allow passing the client secret.

Suggested changes are

• Add a property ClientSecret to the RequestOptions Object
• In Requestor.GetRequestMessage (or in SourceInstance.InstanceUrl, or where applicable) read the ClientSecret value and add it to the request

[remi-stripe]

@alessandroghizzardi Thanks for the report! I think we will instead change the prototype of Get to allow you to pass a custom Options class that would have ClientSecret. We're going to work on a fix and hopefully release it next week.

[ob-stripe]

@alessandroghizzardi As of v21.2.0, you can do something like this:

var options = new SourceGetOptions
{
  ClientSecret = "src_client_secret_123",
};
var source = sourceService.Get(sourceId, options);

[alessandroghizzardi]

@alessandroghizzardi As of v21.2.0, you can do something like this:

var options = new SourceGetOptions
{
  ClientSecret = "src_client_secret_123",
};
var source = sourceService.Get(sourceId, options);

Top! Thank you!