#jainnikesh
1 messages ยท Page 1 of 1 (latest)
Hi ๐
Hi
What do you mean "pay using an insurance card"?
Do you have an example API request or Payment Intent ID?
Do you know insurance card that is available in usa
So we are using a connected account then when the user tries to pay using the terminal using the insurance card
Then it's giving invalid amount
I still have no idea what you mean by Insurance Card. But let's start with the API request that is throwing the error.
Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
Are you using Stripe?
Yes we are using stripe
And we are creating a connected account for all our customers
Okay so you should be able to provide the API request ID. At that point I can help answer your question
Okay wait
But that transaction never completed
So it's not showing in stripe dashboard
Even a failed API request that throws an error is in your Account logs
In the Stipe Dashboard, if you have access to the Developer Section, you should see any failed API requests in the Logs section.
I'm still waiting on an example. I can't really help more without one
Sha card
An example Payment Intent that shows the error you are referencing. I really need something like that to offer more advise here.
Do you know about different types of cards
So, currently the practices receive virtual credit cards from insurances. These cards are loaded with balances for multiple patients at once. So if there are 10 patients who are insured by the same provider, the insurance will send a card of say $1000 to the practice that will hold the payments for all these 10 patients.
The practices currently create a dummy patient in their EHR ( like say the name is Cigna) and process the cards using this dummy patient and then they have to manually enter the payments for all the 10 patients into the EHR balance.
So this is kind of a workaround that I suggested them and it is working well till date but as the number of patients is increasing, it gets difficult to handle.
I might be able to offer some insight if you provided an example of the errors you were mentioning ealier
I am getting only invalid amount
On what?
When user try to do payment using insurance card
{
"error": {
"code": "card_declined",
"decline_code": "invalid_amount",
"doc_url": "https://stripe.com/docs/error-codes/card-declined",
"message": "Invalid amount.",
"param": "",
"request_log_url": "https://dashboard.stripe.com/logs/req_h4KASg32OXO6kY?t=1679596077",
"type": "card_error"
}
}
POST /v1/payment_methods/pm_1MosrgFRSoISGwgOqva8BBNx/attach
Thank you. That request log URL is what I've been asking for this whole time
๐ We're still looking - please be patient!
The reason this is failing is because we run a validation on the card when it's attached to a customer. The card issuer is declining that validation with a decline code meaning "invalid_amount"
Sha or acha kind of
If you don't want this validation to be happening you need to be passing "validate: false" when you attach the PaymentMethod to your customer
What type of validation are you doing
Like that card have amount or not ?
Because previously same this happened for another connected account
We're just validating the card with the issuer to ensure it's a valid card
But something we did for that account then their customers now able to use insurance card
This is happening only for insurance card
Again, this is a decline that is coming from the card issuer themself - it's not coming from us so there isn't a "setting" on your stripe account that would change this. The only thing that you could do is bypass the validation by passing validate: false when you make the attachment call
But that is risky right to passing validation false
So there must be some other way
There must be something that I have to enable
Again, there's no setting or "thing you have to enable"
THis is purely a decline on the card issuer's end
Really what you should be doing is using SetupIntents to collect card details, but for you specific flow (or creating the PM and attaching it) the only way to use that card would be for you to bypass the validation on that attachment call
So there is no risk ?
The only risk would be that you save payment methods that don't work - but you can confirm whether they work or not when they're actually used for payment