#k3davis

1 messages · Page 1 of 1 (latest)

snow willowBOT
lunar tiger
#

Please share examples

dry musk
#

req_CXgxQTg7KWLrUo

#

req_BJceVcHo0fHjUf

#

can provide others if helpful

lunar tiger
lunar tiger
dry musk
#

They are still successfully charging at the other vendor (cybersource), nothing we can do but abandon them then? :/

lunar tiger
#

Umm, my assumption is it pertains only to attempts made us Stripe (not the other PSP)

dry musk
#

I mean to say that we know these cards are good because they succeed elsewhere. I'm just asking if the failures to setup in stripe are due to something we're doing, or if there are other reasons stripe wouldn't be able to accept a known good card from another vendor.

#

Just making sure you understand what I'm asking, that doesn't mean your answer is any different 😉

lunar tiger
#

To be clear, you're trying to migrate PAN data from one provider to another yourself? Did you consider using our migration services for this?

#

This would be the far more efficient way of migrating to Stripe

dry musk
#

Yes I understand. In this case we've had the tokens internally ourselves up until now, so essentially we are the other provider. And we've had just over 100 that don't convert out of more than 10,000 (all the non-guest customers in our account)

lunar tiger
#

Yeah there's nothing wrong with the requests you've shared from an integration perspective really

dry musk
#

ok. thank you for taking a look.

lunar tiger
#

Maybe those cards are cancelled or something?

dry musk
#

i've confirmed that (at least some of these, like these examples) still work when charged against cybersource after being declined for setup in stripe

#

but this is probably not something you can help me with if the integration looks ok.

lunar tiger
#

Yeah one specific example was transaction_not_allowed (you can see in the response) which is a bank decline error they're returning to us. We wouldn't know what specific isn't allowed