#kenil-d-hyperlink-infosystem_afterpay

1 messages · Page 1 of 1 (latest)

solid perchBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1252574772412284948

📝 Have more to share? Add details, code, screenshots, videos, etc. below.

gusty escarp
#

I encountered an error while trying to add a payment method to save a card. Why am I getting this error in test mode?
Because you are sending raw card details via the API

solid perchBOT
#

💁 What you can share safely

This is a public server. Anyone can see the messages posted here, so you need to be careful when sharing certain information.

🛑 Not safe to share

Do not share anything sensitive or privileged on Discord, including the following:

  • 🛑 Secret API keys (most Stripe secret API keys start with sk_, rk_, or ek_)
  • 🛑 Secrets (examples include Stripe's client secrets, which contain _secret_, and Stripe's webhook signing secrets, which start with whsec_)
  • 🛑 Passwords, keys, or other login/authentication details
  • 🛑 Information about non-public features or functionality

If you don't want something public, don't share it here.

✅ Safe to share

Stripe object IDs are safe to share in public, and are often required to help us investigate and debug issues. Some examples of IDs you can share safely are:

  • ✅ Customer IDs (cus_)
  • ✅ Checkout Session IDs (cs_)
  • ✅ Subscription IDs (sub_)
  • ✅ Invoice IDs (in_)
  • ✅ Setup Intent IDs (seti_)
  • ✅ Payment Intent IDs (pi_)
  • ✅ Charge IDs (ch_ and py_)
  • ✅ Request IDs (req_)

This list isn't comprehensive; there are too many Stripe object IDs and prefixes to list that are safe to share publicly.

If in doubt, ask someone on this server with the Stripe Staff role if a particular piece of information is safe to share before you share it.

gusty escarp
soft smelt
gusty escarp
#

You shouldn't be sending raw card

#

You need to follow the guide I shared with you above

soft smelt
#

please share me any refrence for save card on server side with help of api or npm?

gusty escarp
#

No you can't save card details on your server. You need to be PCI compliant

soft smelt
#

okay please know me how to save card into stripe with help of npm or api.

gusty escarp
solid perchBOT
paper trench
#

👋 taking over for my colleague. Let me know if there's any follow-up Qs I can answer!

solid perchBOT
soft smelt
#

I created a payment intent with Afterpay as the payment method, but the Afterpay option is not appearing on the client side.

solid perchBOT
#

kenil-d-hyperlink-infosystem_afterpay

paper trench
#

what's the PaymentIntent ID?

soft smelt
#

pi_3PRbJ4LLpJGCnaR90RUokXzi

paper trench
#

do you have a return_url in your payment element?

soft smelt
#

const paymentIntent = await stripe.paymentIntents.create({
amount: (body.amount * 100), // Amount in cents
currency: 'aud',
customer: stripe_customer_id,
metadata: body.metadata,
automatic_payment_methods: {
enabled: true,
}
});

i am enable automatic_payment_methods is true but don't show in client side only show card payment

paper trench
#

do you have an accessible url where I could test this out in test mode?

soft smelt
#

sorry currently no any accessible url.

#

please close this thread