#sruilova-apple-pay-recurring

1 messages · Page 1 of 1 (latest)

cunning nest
#

Note that Apple has some rules around using Apple Pay with recurring payments, so you need to make sure you fall into a supported use case

#

But other than that you'd provide the saved Apple Pay payment method id on the payment intent or subscription

#

Can you provide more detail about your use case?

faint fractal
#

But when I create another paymentIntet to charge a service, which token or key I use, why do I store the PaymentMethodId to use it but it won't let me.

cunning nest
#

Can you rephrase that? Sorry I don't understand what you mean. Have you already saved the payment method / attached to a customer?

faint fractal
#
  1. Create a PaymentIntent secret to send to the client
  2. I check the PaymentIntet id that the client sends me when everything is ok, and I update with a customer.
  3. I can no longer use the payment method for a new charge.
cunning nest
#

Yes, you need to make sure you save that for future payments:

#

using setup_future_usage

faint fractal
#

I use the following code:

PaymentIntentCreateParams params =
PaymentIntentCreateParams.builder()
.setAmount(1099L)
.setCurrency("usd")
.build();

PaymentIntent intent = PaymentIntent.create(params);
String clientSecret = intent.getClientSecret();

Where do I use that setting?.
How to configure the payment method to be able to use it and that a client is tied?

cunning nest
#

It is a parameter fore the payment intent, yes, so part of your create parameters

faint fractal
#

Español
Inglés

By default the payment method is created with a customer in a null state, so I can no longer use that payment method

cunning nest
#

You'll want to create the customer and provide that with the payment intent params, too

#

(or provide a pre-existing customer)

faint fractal
#

ok, thank you very much now I'm going to do tests.

cunning nest
#

👍