#meeelaardiayon_code

1 messages Β· Page 1 of 1 (latest)

atomic ibexBOT
#

πŸ‘‹ 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/1234311354505232426

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

errant monolithBOT
remote anchor
patent bison
#

Can you share which integration doc this integration is on and also the code in your video? It'll be helpful to share the public accessible URL of this website as well

remote anchor
#

This is our original code

remote anchor
remote anchor
remote anchor
patent bison
#

In the code of this video, I don't see submit() being called anywhere.

Why are there three sets of integration in your code - Split Card Element, Payment Element and embedded Checkout?

#

Which one is throwing the error?

#

Can you simplify the code to the integration type that is having the issue?

#

There should only be one integration type in a checkout flow

remote anchor
#

Okay, we will simplify the code. Give us 5 mins please.

patent bison
#

Can you also share the URL of your development website?

remote anchor
patent bison
remote anchor
#

We need to use the the payment and the creation of tokenisation separately

#

We have 2 test cases

  1. Process the payment and pass metadata parameters.
  2. Create a customer from card element - no payment involve
#

@patent bison we also confirmed that stripe elements are not compatible with old orgs. We test it on one of our old developer org that was created last 2015.

patent bison
#

we also confirmed that stripe elements are not compatible with old orgs. We test it on one of our old developer org that was created last 2015.
I'm not too sure what this means. Are you referring to Stripe account?

We need to use the the payment and the creation of tokenisation separately
Am I right that you would like to use Split Card Element to create a payment method first, then make a payment if necessary?

remote anchor
#

We need to split because we need to pass metadata before the payment attempt

remote anchor
remote anchor
patent bison
remote anchor
#

Ah yes, we are aware of that one but our challenge is on the 3rd step. We can't proceed to payment but there were no error log. So are not sure where to start debugging and can't see what's in the payment function.

patent bison
#

How did you handle the third step? It should be just stripe.confirmCardPayment with payment_method. However, I don't see it in your code

remote anchor
#

@patent bison we've tried the code from glitch but same issue.

patent bison
#

If you only use vanilla HTML and JS (Not in lightning web component), does it work?

remote anchor
#

It will sure work I suppose

#

Is there any way we can debug the library?

patent bison
#

I'm afraid we don't know how lightning web component works. It's likely that there are third-party library or plugin preventing it from working

remote anchor
#

Is there any explanation as to why there is a response during validation e.g. expired card, wrong client secret but no response during payment attempt?

patent bison
#

Which response are you referring to? What is the function you attempt to call?

#

Is it stripe.confirmCardPayment()?

remote anchor
remote anchor
patent bison
#

error is expected to be empty if there is no error

#

Did you log entire response from stripe.confirmCardPayment(). For example,

const result = await stripe.confirmCardPayment(...);
console.log(result);
#

I don't see that in your code

remote anchor
#

Please refresh on your end @patent bison

#

We updated the code

patent bison
#

What should I refresh?

#

This is the error I faced

image.png
remote anchor
#

Yep, please refresh again. We provided the right access, aplogies.

patent bison
remote anchor
#

That's our problem

#

we can't get it to pass confirmCardPayment

patent bison
# 
let r = {};
r = {
    payment_method: {
        card: t._cardNumberElement
    }
};

This doesn't look right to me. Are you passing payment method ID or card element?

#

Sorry! I double check the confirmCardPayment(), the spec looks correct to me.

Can you log t.getStripe and see what's inside? When I put a break point on const a = yield t.getStripe.confirmCardPayment(s, r);, nothing went through

image.png
remote anchor
#

Okay sure. No problem.

errant monolithBOT
patent bison
#

I can't spot any issue. If you don't use t.getStripe, but use:

const stripe = Stripe('pk_test_xxx');
stripe
  .confirmCardPayment('pi_xxx_secret_xxxx', {
    payment_method: {
      card: cardNumberElement,
    },
  })
remote anchor
#

@patent bison so u mean, no issue with the code?

slender zephyr
#

Hi @remote anchor I'm taking over this thread.

remote anchor
#

Hello @slender zephyr good afternoon

slender zephyr
#

It's a long thread, is your latest question about why 't.getStripe.confirmCardPayment` not getting called?

remote anchor
#

Yes, that's right.

#

River confirm that it did not go through

slender zephyr
#

Have you tried what river suggsted? i.e. using stripe directly?

remote anchor
#

It did not go through as well

slender zephyr
#

This page asks for login

remote anchor
#

Sorry, send the wrong one