Tanu

[narrow hedge]

And are they not showing up as you expect? Where do you expect them to be available?

[surreal gulch]

Now you've the full context i guess.

[narrow hedge]

Can you share a pi_xx ID?

[surreal gulch]

pi_3N6ABZFAD0UVeEWG1EHkbwMW

and in the dashboard, stripe location is set to Singapore.

[narrow hedge]

Let me see

[surreal gulch]

cool. thanks

[narrow hedge]

Ok, PayNow should be valid and available in the Payment Element

Doesn't look like Grabpay is correctly enabled on the account

Which UI are you using?

[surreal gulch]

nextjs

and node for server

[narrow hedge]

No, which Stripe UI Element. I'd assume the Payment Element? https://stripe.com/docs/payments/payment-element

Or is it the older Card Element?

[surreal gulch]

payment element it is

[narrow hedge]

Can you share the code?

[surreal gulch]

code for creation of paymentintent or payment element?

[narrow hedge]

Your front-end Next.js code

[surreal gulch]

const options: any = { clientSecret, appearance, loader, fonts: [ { family: "satoshi", src: url(https://${
typeof window !== "undefined" && window.location.origin
}/assets/fonts/Satoshi-Regular.woff)`,
},
],
};

return (
<div>
{clientSecret && stripePromise ? (
<Elements key={clientSecret} options={options} stripe={stripePromise}>
<PaymentForm clientSecret={clientSecret} />
</Elements>
) : (
<div className="container text-center">Loading...</div>
)}
</div>
);`

This is for paymentform:

` <div>
<PaymentHeader />
<div className="container mt-4">
<div className="flex items-center space-x-2">
<button type="button">
<TbArrowNarrowLeft className="w-6 h-6 text-neutrals_4" />
</button>
<span className="text-lg leading-6 text-neutrals_1 font-bold">
Complete your payment
</span>
</div>
<form id="payment-form" onSubmit={handleSubmit}>
<div className="mt-5 space-y-9">
<LinkAuthenticationElement
id="link-authentication-element"
onChange={(e: any) => setEmail(e.value.email)}
options={{
defaultValues: {
email: "[e-mail]",
},
}}
/>

        <div className="mt-9">
          <h2 className="text-neutrals_2 text-base font-bold">Address</h2>
          <AddressElement
            options={{ mode: "billing", allowedCountries: ["US"] }}
            onChange={(event) => setAddress(event.value)}
          />
        </div>
        <div className="mt-9">
          <h2 className="text-neutrals_2 text-base font-bold">
            Credit card information
          </h2>
          <PaymentElement
            id="payment-element"
            options={paymentElementOptions}
          />
        </div>
      </div>

      <Button
        className="primary-btn w-full mt-9"
        disabled={!stripe || !elements}
        isLoading={isLoading}
        isSubmit
      >
        <span>Complete Payment</span>
      </Button>
      {/* Show any error or success messages */}
      {/* {message && <div id="payment-message">{message}</div>} */}
    </form>
  </div>
</div>`

[narrow hedge]

Well, PayNow is for SG customers only. And according to https://dashboard.stripe.com/test/logs/req_1WCLJOxCPCRsvG you're based in IN: https://stripe.com/docs/payments/payment-methods/integration-options#country-currency-support

[surreal gulch]

yeah, we have tried with vpn. But it's just the same.

[narrow hedge]

Well, GrabPay isn't turned on here: https://dashboard.stripe.com/settings/payment_methods

As for PayNow, is there somewhere I can reproduce the issue? As according to our logs for pi_3N6ABZFAD0UVeEWG1EHkbwMW is should be available. You can even see it's included in the creation response:

payment_method_types: [
    "card",
    "paynow",
  ],

[surreal gulch]

yeah, i can see paynow. But my concerns are just for grabpay.

[narrow hedge]

As stated, it's not enabled

Sorry, I misread your original message. I thought you said you couldn't see either PayNow or GrabPay

But yeah, GrabPay isn't turned on

[surreal gulch]

i've been told they have enabled grabpay too from dashboard. Anyway, I've asked them again.

[narrow hedge]

When I checked ~25 minutes ago it wasn't

Checked again, still disabled

[surreal gulch]

I've forwarded this to team. Will get back to you, when i here something from them.

Thanks for your time.

But here's a one more thing, when we were explicitly passing ["card", "grabpay", "paynow"] as value of payment_method_type instead of automatically enabling payment methods , we were able to see grabpay on UI.

As you're saying that it isn't turned on, then how come it didn't throwing us an error.

[narrow hedge]

But here's a one more thing, when we were explicitly passing ["card", "grabpay", "paynow"] as value of payment_method_type instead of automatically enabling payment methods , we were able to see grabpay on UI.
Yep, that's how it works in test mode. You can explicitly pass any type to p_m_t parameter and it'll be supported

But AutoPMs respect the Dashboard settings

[surreal gulch]

i see

[fierce dock]

Hey, taking over here. Let me know if there's any follow-up Qs I can answer!

[surreal gulch]

cool.

My query's been resolved. Thanks @narrow hedge.