#nickdnk

1 messages ยท Page 1 of 1 (latest)

signal nightBOT
#

Hello! We'll be with you shortly. 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.

dusty pagoda
#

Is that the angle that you are getting at or did I miss the question?

marble scroll
#

I need acct_1BoB66Lj11Ytqxjb in test mode to not perform currency conversion to USD when accepting payments in DKK

#

For context, we force our users to only accept payments in the same currency as their stripe default currency

#

As storing fees and whatnot in varying currencies is an absolute nightmare

#

I managed to change its country to DK, but what do I do here?

#

It wants a bank account, but I assume it has to be DKK to not perform conversion?

dusty pagoda
#

Uh with "Denmark" selected, of course ๐Ÿ˜…

marble scroll
#

Okay I think that works

#

Let me try

#

Yep that did it

#

Thanks a lot, that has been bothering me for a long time ๐Ÿ˜„

#

Something you may want to consider is to delay the events for dispute-triggering cards by at least a few seconds. It's coming in before I can even capture the charge, see the order of events for pi_3ODBvRLj11Ytqxjb19yjjXze

#

(this test was before I fixed the currency conversion)

dusty pagoda
#

Gotcha, thanks for the feedback. I will file something for that. I could have sworn we did that before but I may be misremembering

#

Definitely agree that the delays are helpful for a lot of testing

marble scroll
#

There is a delay on test outcomes in the identity verification webhooks

#

so maybe that's what you think of

dusty pagoda
#

Yep now that I think of it, I was thinking of either that or our bank payment methods that make intents go in to a processing state each have test numbers that delay things like that

marble scroll
#

In my case this was still handled gracefully, but having the capture happen after a dispute might cause all sorts of unexpected states in other people's systems