#jainnikesh_api

1 messages ยท Page 1 of 1 (latest)

blissful copperBOT
#

๐Ÿ‘‹ 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/1283069026871935039

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

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

storm quiver
#

Hello

#

pi_3POMH1FRSoISGwgO0PKc2IF9
pi_3POMGZFRSoISGwgO10oVmaJK
pi_3POMLHFRSoISGwgO0oWDEs1o

pi_3PQYZFFRSoISGwgO0wTdpOnz

pi_3PlBiDFRSoISGwgO1IIM6LbI
pi_3PiKtkFRSoISGwgO1nPIcqh9
pi_3PiKYqFRSoISGwgO18tsrDo4
pi_3PiKXmFRSoISGwgO07exVQKi

pi_3PktnrFRSoISGwgO09ha0W9A
pi_3PktnEFRSoISGwgO0cOJKkHn

pi_3Pkpd1FRSoISGwgO1HbNDvc0
pi_3Pkpn3FRSoISGwgO1JjLEUe7

pi_3MydYhFRSoISGwgO0HgwBQa4
pi_3MydY0FRSoISGwgO1YO24PTy
pi_3MydXSFRSoISGwgO1LkuZdzg

#

this all payments failed

#

and bank mentioned that because you are doing recuring payments

#

can you please help in api side how single and recuring payment can be differ

#

and what flag or code i have to add while taking payment

#

stripe.paymentMethods.attach(reqData.source, {
customer: customer
}).then((customerCardSource) => {
stripe.paymentIntents.create({
amount: amount,
currency: reqData.currency || 'usd',
description: reqData.description,
customer: customer,
payment_method_types: ['card'],
payment_method: reqData.source,
metadata: reqData.metadata,
application_fee_amount: fees,
setup_future_usage: 'off_session',
transfer_data: {
destination: accountId,
},
on_behalf_of: accountId,
confirm: true
}).then(async (payment) => {
stripe.charges.retrieve(payment.latest_charge, { expand: ['balance_transaction', 'balance_transaction.source'] }).then((charge) => {
charge.balance_transaction.client_secret = payment.client_secret;
resolve(charge.balance_transaction);
}).catch(err => {
reject(errorHandling(err));
});
}).catch(err => {
reject(errorHandling(err));
});

#

here is my code

shadow gazelle
#

Hi ๐Ÿ‘‹ did the bank give you any more details on why they thought that? Payment Intents are for single payments, the only thing standing out to me about them (I've only had a chance to look at the first one so far) is that you're using setup_future_usage set to off_session. That's typically done to prepare a Payment Method for future off-session (recurring) payments.

storm quiver
#

i have lots of customer complaining their insuarance card not working or declined

#

after that they go with insurance provider and then bank

#

and for all the payments bank and insurance provider saying about recuring payments

#

but stipre saying something else pi_3POMH1FRSoISGwgO0PKc2IF9

-Payment declined

pi_3POMGZFRSoISGwgO10oVmaJK

-Payment declined

pi_3POMLHFRSoISGwgO0oWDEs1o

-Payment declined

pi_3PQYZFFRSoISGwgO0wTdpOnz

-Payment declined

pi_3PlBiDFRSoISGwgO1IIM6LbI

-Payment declined by the issuing bank

pi_3PiKtkFRSoISGwgO1nPIcqh9
-Payment declined by the issuing bank

pi_3PiKYqFRSoISGwgO18tsrDo4

-Payment declined by the issuing bank

pi_3PiKXmFRSoISGwgO07exVQKi

-Payment declined by the issuing bank
pi_3PktnrFRSoISGwgO09ha0W9A

-Payment declined

pi_3PktnEFRSoISGwgO0cOJKkHn

-Payment declined

pi_3Pkpd1FRSoISGwgO1HbNDvc0

-Payment declined

pi_3Pkpn3FRSoISGwgO1JjLEUe7

-Payment declined

pi_3MydYhFRSoISGwgO0HgwBQa4
-Payment failed because card was reported stolen

pi_3MydY0FRSoISGwgO1YO24PTy

-Payment failed because card was reported stolen

pi_3MydXSFRSoISGwgO1LkuZdzg
-Payment failed because card was reported stolen

shadow gazelle
#

These are being declined by the issuing banks, so they're better suited to explain why they've blocking them. But these aren't flagged as recurring on our end.

storm quiver
#

first we are doing stripe.paymentMethods.attach( and then stripe.paymentIntents.create(

#

so in this code anything we are doing wrong ?

#

when i discussed with stripe support they said

shadow gazelle
#

No, nothing seems to be wrong as far as I can tell. You're successfully creating Payment Intents, they're going to the issuing bank, and the issuing bank is declining them. Again, if the banks are blocking you from setting up the cards for future recurring payments, then the use of setup_future_usage may need to be adjusted to fit their requirements. But that also impacts your flow as the Payment Method won't be set up for future off-session payments, however that may be fine if you aren't processing recurring payments.

storm quiver
#

SO IF WE REMOVE THIS THEN WHAT IT WILL EFFECT

shadow gazelle
#

If you're not processing recurring payments, nothing. You can test removing it in your flow in testmode first and confirm it won't impact any of your downstream processes.

storm quiver
#

ok

#

yes we want only one time

#

payment

#

not recuring payment

#

and anything else you see wrong in our code

shadow gazelle
#

That's why I'm confused, these are one-time payments. I'm not sure what the bank is referring to when they say they're recurring.

storm quiver
#

bank saying you are doing recuring payment that is why declined

#

Client is not able to process any Mutual of Omaha insurance payments since April 10th.
They (Insurance company) said to tell you to remove the zero dollar test on your end so their VCC payments will process. bank saying that recuring payment is enable that's why declined all are declines bank mentioned that your account have recuring payment enables that's why declines can you

#

wait

#

i have question

shadow gazelle
#

They aren't recurring payments. Trying to remove setup_future_usage is the only thing coming to mind without more clear context from the bank.

shadow gazelle
storm quiver
#

stripe.paymentMethods.attach(reqData.source, {
customer: customer
}).then( here we are stroing card

#

so wil;l it affect as recuring card ?

shadow gazelle
#

Recurring cards aren't a thing

#

Attaching them can cause some validations to occur, but your attachment requests are all succeeding?

storm quiver
#

because when we store card we can take payment again

#

so insurance card are failed

#

because of this reason

#

i am not sure

#

can you help

shadow gazelle
#

I'm sorry, it's really hard without more context. The Charge objects that are being created for these Payment Intents aren't recurring, so the best I can do is guess at what the bank means when they say they are.

#

If you aren't planning to process recurring payments, there are some things I might suggest changing.

Does you flow need to have a Payment Method object before you create the Payment Intent? Are you inspecting that for any reason before payment?

storm quiver
#

what means storing details ?

#

will it casue any issue

#

or only setup_future_usage: 'off_session',

#

this is problem

shadow gazelle
#

I don't know, I don't know why the bank is declining these so I don't know what exactly you should be changing. I do strongly suggest trying to remove setup_future_usage, but then you asked for other things you can improve.

Right now your flow is:

  • Create a Payment Method from the Card Element
  • Attach that Payment Method to the Customer
  • Create a Payment Intent for the Customer using the previously created PM

but that can be reduced to:

  • Create a Payment Intent for the Customer
  • Confirm the intent clientside using the details collected from the Card Element

I would suggest considering this simplicifaiction, but I'm not familiar with your flow so I don't know if you need to look at the Payment Method you create before creating the Payment Intent, and was trying to get that insight.

storm quiver
#

creating payment link using first option and ask client to do payment using insurance card will help ?

shadow gazelle
#

I don't know. Payment Links still create Payment Intents which create Charges, so when they're being sent to the bank they'll be very similar to what you have now.

storm quiver
#

okay then how i can check

shadow gazelle
#

You get more context from the bank explaining why they declined the payments so we have a better idea of what you need to consider changing, or you try my previous suggestion (first testing in testmode to make sure it won't break your flow) and see if that helps.

storm quiver
#

ok

#

thank you so much