Initial pass at Plaid EU

[Shpigford]

No description provided.

[Shpigford]

@zachgoll First high-level pass at adding EU support. You've got a better handle of how the Plaid stuff works, so let me know if I'm off base here.

[zachgoll]

I reached out to Plaid and they said there is no way to figure out whether an "Item" is US or EU just based on the Plaid Item data.

So the biggest thing we're missing currently here is that identifying piece of data stored on PlaidItem. I think since there are only 2 possible clients, we could consider a field called plaid_region that is a string and in our model we could probably validate that too:

class PlaidItem < ApplicationRecord
  enum :plaid_region, { us: "us", eu: "eu" }
end

Which would then allow us to easily access it like, some_item.eu?

Otherwise, I think EU should work largely the same as US and I believe our existing implementation will properly handle these multi-currency accounts fine.

[Shpigford]

@zachgoll Take a look now.

[zachgoll]

Yeah, I like this strategy of passing it from the Stimulus controller. Should work nicely!

[Shpigford]

@zachgoll Two things I'm not sure on...

1. Do we need to add Canada ("CA") to the region stuff? Or will "US" properly cover it thanks to get_country_codes?
2. There are failing system tests that I'm not familiar enough with to not potentially completely break them.

[zachgoll]

@Shpigford to my understanding, you have the CA configuration correct here. I believe CA is fully covered under the "US" client:

[Shpigford]

@zachgoll ✅ Anything else before merging this?

[zachgoll]

@Shpigford I think we're all set. Only thing I can think of is making sure these are set in prod:

PLAID_EU_CLIENT_ID=
PLAID_EU_SECRET=

[henrikbjorn]

Not to hijack, but would GoCardless be an idea also? That is easily obtainable for self-hosting.

[Shpigford]

Not to hijack, but would GoCardless be an idea also? That is easily obtainable for self-hosting.

#141