#ranvir_ApplePay

1 messages · Page 1 of 1 (latest)

regal shuttle
#

They should be supported

#

Did you work for PaymentIntent not not for SetupIntent?

#

(I want to be sure your settings about domain etc is correct)

tribal sedge
#

SetupIntent is what I am looking at, not the PaymentIntent

# 
var path = "/v1/setup_intents";
            var bodyParameters = new[]
            {
                new KeyValuePair<string,string>("payment_method_types[]", "nz_bank_account"),
                new KeyValuePair<string,string>("payment_method_types[]", "card"),
            };
            var request = new HttpRequestMessage(HttpMethod.Post, path);
            // request.Headers.Add("Stripe-Version", "2017-08-15;nz_bank_account_beta=v1");
            request.Headers.Add("Stripe-Version", "2020-08-27");
            request.Headers.Authorization = new AuthenticationHeaderValue("Basic", Convert.ToBase64String(Encoding.UTF8.GetBytes($"{apiKey}:")));
            request.Content = new FormUrlEncodedContent(bodyParameters);
            var httpClient = new HttpClient();
            httpClient.BaseAddress = new Uri("https://api.stripe.com");
            var response = await httpClient.SendAsync(request);
            return await response.Content.ReadAsStringAsync();

Here I create the SetupIntent client secret

regal shuttle
#

I know, but have you ever succeed with PaymentIntent, or you simply started with SetupIntent?

#

There is a high chance about not setting up ApplePay domain correctly

tribal sedge
#

ohh, well for negate that factor I was trying GooglePay. and yes havn't tried PaymentIntent, I should have tried that.

#

The way I setup this sample code, was run locally, serve on https and access it on Android emulator

regal shuttle
#

Okie so it could be different between ApplePay and GooglePay. Each has conditions to be met, and I believe those conditions are the same for PaymentIntent vs SetupIntent

#

Does your logged in Google Account has card setup?

tribal sedge
#

Yes it was setup, so as you said I can try with PaymentIntent and then change it into SetupIntent. But you confirm that SetupIntent, can be done using these 2 wallets? So we capture the details and raise a invoice later to charge the customer based on the invoice. I saw one more comments somewhere in the group that these wallets need user presence and hence cannot be done off-session That was slightly confusing.

regal shuttle
#

I know that comment. Generally it's ok (and possible) to use ApplePay/GooglePay with SetupIntent, since you create an agreement with the customer "I will charge this later, once". But it's not okay (still possible, but could be declined) if you use the saved PM with SetupIntent and charge them multiple times later on

#

SetupIntent should work with those 2 wallets. Most of the time it's not working is because of the prerequisites conditions, as we see frequently...

#

I can quickly try myself (brb)

tribal sedge
#

On the note - "I will charge once and not multiple times." Well here the intention is to charge the customer multiple times, based on raised invoice amount. On the contrary the subscriptions acts differently,, right?, which is fixed amount every month or year.

regal shuttle
#

Then it's the case you shouldn't do that. It against Apple/Google TOS. They want each time a customer is charged, the customer should be present with the ApplePay/Google Sheet, aka don't silencely charge them. Subscription is different be cause they are treated as recurring Payment, and Apple/Google is okay with that

#

The tricky part is that, you still can do it, but it's not guaranteed to be succeed. It could be declined later on, and hurt your risk score as a merchant (I don't quite have details about this part, but I believe Apple or Card network or issuer bank does maintain their own risk score system)

regal shuttle
#

(Just tested myself to confirm that wallet does work with SetupIntent, on web)

tribal sedge
#

cool thanks, I must cascade this info to the team and we assess its implementation. highly appreciated. 🙂