11
Recurring donation should be sent in correct currency
in progress
Activity
Newest
Oldest
Michele O'Neill
It might be helpful to mention that not all of our regular donors got charged in the wrong currency. We have about 25% of affected regular donors who donated in any other currency than a default one (GBP) on our multicurrency form. That is since we implemented GiveWP on our site (March this year). On top of that, two of the donors were charged in a completely different currency than GBP on the same donation form.
We've just done a workaround to create a separate form (and page) per each currency whilst using the three most used currencies and disabling others.
Michele O'Neill
We have the same problem with our default form with multiple currencies. When donors donate regularly via GBP, that's fine (as that's the default currency for that form), but if they choose any other one, the donor is charged in GBP and wrong amount. GiveWP receipt shows incorrect currency and amount too, only Stripe receipts are correct.
We don't have the same problem with our US form, as there is only one (USD) currency, that's the default one for that form.
Ravinder Kumar
in progress
David Stark
Very serious.
A similar issue has happend to at least 20 of our donors. Our base currency is £GBP. In most cases (17) the donations were processed in $USD, which is less concerning because all it means (!) is that we lost out on money due to exchange rates. In the other cases, the donors were paying in other currencies and were charges in £GBP. In the case of a South African donor the exchange from 25 RAND to £25 nearly wiped him out. Similarly with $CAD, where we took double what they wanted to give.
This is a really significant bug and we are happy to provide any access you need to our live site to figure it out.
Also, because the reported amounts are GBP we have claimed this as Gift Aid, when we actually only received less ($) which means we are falling foul of the taxman!
C
Christopher Rachal
Any ETA on this?
Ben Meredith
under review
We've seen reports of this a few times now, and as of yet have been unable to replicate the problem in our tests. That usually means that some setting is different in our Stripe account than those experiencing the issue, or some specific server/host configuration.
We're keen to resolve the issue for the folks experiencing it, but at this point we're stuck until we get some steps to replicate the problem. Please vote and comment here with steps to replicate the issue.
Julian Rush
Ben Meredith: I have this issue. My user case:
Active Give addons: Recurring Donations, Currency Switcher, Per Form Gateway, Gift Aid, PDF Receipts
Currency settings: Base - GBP
Currency Switcher (global settings):
Auto-switch: enabled, Active currencies: GBP, USD, EUR, NZD
Geolocation: disabled
Gateways: all currencies - Stripe CC, PayPal Standard, Offline, Google Pay, Apple Pay. GBP only - GoCardless
Form settings:
Template: Legacy form, All Fields
Options: Set Donation: GBP 1000, Recurring: Admin Defined, yearly for 3 years, Custom Amount: enabled, Donation Limit: Min (GBP) 1000, Max (GBP) 999999.99, Custom Prices: enabled, USD 1000, EUR 1000, NZD 1000
Fields: Guest Donations: disabled, Registration: Registration + Login, Anonymous: enabled, Comments: enabled
Goal: disabled
T&C: custom
Offline: global
Stripe: default account
Gift Aid: global
PDF Receipts: global
Currency Switcher: global
Emails: global
Confirmation: global
Per Form Gateway settings:
All gateways enabled (Stripe CC, GoCardless (GBP only), PayPal Standard, Offline, Google Pay, Apple Pay)
A US donor has twice tried to create a subscription for USD 1000. Both times, it was registered in Give as a USD subscription but the donor was charged by Stripe for GBP 1000. All previous subscriptions through this form have been in GBP so this was the first attempt at a USD subscription.
He had previously successfully donated in USD via Stripe with the same credit card via a different (non-subscription) form.
The error appears to start with Give as Stripe logs show the initial request from Give had no currency details. Either the Stripe base currency (GBP) was used by default or Stripe used the previous currency for the product, also GBP, rather than the donor's previous currency, USD. Give did not seem to try to create a new Stripe product/plan for USD as it has for another subscription form on the site.
Stripe log of initial request from Give:
{
"customer": "cus_<redacted>",
"items": {
"0": {
"plan": "become-a-patron_100000_year_1"
}
},
"metadata": {
"Email": "<redacted>",
"Donation Post ID": "8004",
"Sequential ID": "OUF-5370",
"My GDPR": "Subscription confirmed"
},
"default_payment_method": "pm_<redacted>"
}
C
Christopher Rachal
Ben Meredith: I have this issue with Authorize.NET and it is replicable. Any solutions for that payment gateway? I have a staging site and can replicate it if need be for testing.
R
Robin Knox
Ben Meredith: We are experiencing more issues with user now, it's starting to get out of hand. It use to just be with USD and GBP but now its with other currencies as well.
Matheus Martins
Christopher Rachal: Hey there. You said that it's replicable. Can you give us steps to replicate this issue?
Looking forward to helping you get to the bottom of this!