#Mister
1 messages · Page 1 of 1 (latest)
Do you have an ID of a payment that was created like this?
Yes I have dozens of them
And what kind of ID you are working with that you are trying to attach here?
I have a card_id which I'm trying to attach to a customer
I also have fingerprint that I can attach to a customer but seems like I cannot do that via api end points
@zenith galleon Here is an example of what I'm talking about https://share.getcloudapp.com/llu7nGej
(Ofcourse that's from test data)
Would you mind copy pasting the text of that card_16m... ID and pasting it here? Easier for me to work with
Sure thing
card_16mRbdGLmxudJHaPjdqyO75h
Thank you. So that is a source object so it should be able to be attached to a customer object. When you try are you getting an error? I'm guessing the issue may be that sources are single use unless already attached to a customer, so if it has already been used in a payment you may not be able to attach it.
hmm when I attach the source object to a customer it throws no such token: card_...
So if it's used in payment what's the alternative to attach a card object to the customer?
Hi stepping in and taking a look here
Can you share the request id for when you're seeing the above error? Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
Sure -> req_HYLcIMUeliKxph
I think the issue here is that this request is made in test mode, https://dashboard.stripe.com/test/logs/req_HYLcIMUeliKxph but the card does not appear to be one of our test cards. Can you try this with one our test cards?
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
Ok I don't have the option to create that again since we have moved away from ChargeOver, may be I can try that with a live card?
Do you think this request should work with a live card_id and live customer_id?
https://share.getcloudapp.com/6qubxyjx
Thanks
Testing in live mode is not recommended as it's against your Terms of Services so I would not recommend this.