#celsian_api

1 messages ยท Page 1 of 1 (latest)

upper sunBOT
#

๐Ÿ‘‹ Welcome to your new thread!

โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

๐Ÿ”— This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1361378671662727359

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

pearl nebula
#

Hello ๐Ÿ‘‹

Did you specifically design your front-end integration to use MPANs as we document here?

crisp lichen
#

Yes, we include the "recurringPaymentRequest" along with the related fields.

pearl nebula
#

I'm testing with my own integration but I don't see any different results returned from the Payment Method object.

#

I still think it is using the MPAN, because that's how you have configured it, I'm just not sure where in the Object we return those details.

crisp lichen
#

Ok, we just wanted to verify. Our issue is we're not seeing the subscription in the "Subscriptions" section of the Wallet in the Mac Settings, so we were concerned that it might not be MPAN.

pearl nebula
#

Can you share the JS code you use to create the Payment Element?

crisp lichen
#

  const ApplePayRecurringPaymentRequest ={ applePay: {
        recurringPaymentRequest: {
          paymentDescription: 'Prime',
          managementURL: 'https://x/settings/billing-details',
          regularBilling: {
            amount: selectedPlan.price,
            label: 'Monthly subscription fee',
            recurringPaymentIntervalUnit: 'month',
            recurringPaymentIntervalCount: 1,
          },
        },
      },     
    }

...

<PaymentElement
          onChange={({ complete, value }) => {
            if (value.type === 'card') {
              setShowPrepaidCardDisclaimer(true)
            } else {
              setShowPrepaidCardDisclaimer(false)
            }

            if (complete && !isPaymentElementComplete) {
              setIsPaymentElementComplete(true)
            } else if (!complete && isPaymentElementComplete) {
              setIsPaymentElementComplete(false)
            }
          }}
          options={{
            layout: 'accordion',
            terms: {
              card: 'never',
            },
            defaultValues: {
              billingDetails: {
                email, // adding these values enables the Link payment method to automatically populate
                phone,
              },
            },
            ...(isRemoveStripeExpressComponentOn ? ApplePayRecurringPaymentRequest : {}),
          }}
        />
pearl nebula
#

Hmmm... Okay so there are enough conditionals here that it's possible to not save with these parameters ๐Ÿค”

crisp lichen
#

It's the same code we've been using for the express checkout element which we haven't had any issues with.

#

But we'll walk it again and verify it's always present when ApplePay methods are selected.