Create StripeCountrySpec model and tests

[joshsmith]

Problem

We want a StripeCountrySpec that contains most data from this Stripe API: https://stripe.com/docs/api#country_spec_object

We can use Stripe's id as our id. For now, there will not be an API endpoint in our application to create/retrieve/update/delete these.

Instead, these records will be created and then will be updated regularly with a cron-like job to find the latest information for displaying the form fields that a user might possibly need for creating their Stripe account and verifying their identity, either as an individual or as a company representative.

The StripeCountrySpec will belong to a StripeConnectAccount, and we'll set the stripe_country_spec_id on the StripeConnectAccount in order to render form details out to the user.

We likely need to use embedded fields here in order to handle the deeply nested hash for the verification fields https://hexdocs.pm/ecto/Ecto.Schema.html#embeds_one/3

We probably want to simplify this to a combination of IndividualMinimumVerificationFields, IndividualAdditionalVerificationFields, CompanyMinimumVerificationFields, and CompanyAdditionalVerificationFields schemas, where the key/value pair is the field name (e.g. legal_entity.address.city) and a boolean.

For now, we can probably ignore implementing anything around supported_bank_account_currencies, supported_payment_currencies, and supported_payment_methods. We should track the default_currency, though.

[YuriiZdyrko]

I'd like to start working on this

[joshsmith]

@Banzay anything you need from us directionally to get started? This would be great.

[YuriiZdyrko]

Thanks @joshsmith. I'm finishing draft and have some questions.

1. Where stripe_country_spec_id value will come from? I assume it's going to be sent as a stripe_country_spec_id attribute in stripe-connect-account POST request. Is this ok, considering there's a country attribute already?
2. stripity-stripe doesn't provide ability to fetch Country Specs. It has to be extended?
3. Regarding Embedded Schemas.
   My embedded schemas have two fields: id and disabled.
   Instead of embeds_one I use embeds_many.
   What do you think about this?

defmodule CodeCorps.StripeCountrySpec do
  use Ecto.Schema
  import Ecto.Changeset

  @type t :: %__MODULE__{}
  @primary_key {:id, :string, []}

  schema "stripe_country_spec" do
    field :default_currency, :string

    embeds_many :individual_minimum_verification_fields, CodeCorps.StripeCountrySpec.VerificationFields, on_replace: :delete
    embeds_many :individual_additional_verification_fields, CodeCorps.StripeCountrySpec.VerificationFields, on_replace: :delete

...

defmodule CodeCorps.StripeCountrySpec.VerificationFields do
  use CodeCorps.Web, :model
  @primary_key {:id, :string, []}

  schema "verification_fields" do
    field :disabled, :boolean
  end

...

[joshsmith]

@Banzay running short on time today, so @begedin would you be able to comment on this in the morning?

[begedin]

I'll have to look into the other ones, for for question 2, yes, stripity stripe will have to be updated. I'll create an issue in that repo. - beam-community/stripity-stripe#220

[begedin]

For question 1, when an organization is creating their stripe account in the ember client, they select their country from a dropdown. This is then set to the countryfield when posting the account.

As far as I can tell, the value in this field is in the same format as the id field on the country spec, so we might not actually need a separate field on the stripe connect account. For now, until we figure out more, I think you can assume that this is the case.

For question 3, I think you went a bit to far.

The way I see it, the schema for verification fields should be something like:

field :individual_minimum, {:array, :string}
field :individual_additional,  {:array, :string}

field :company_minimum,  {:array, :string}
field :company_additional,  {:array, :string}

That way, you can easily do an embeds_one

[YuriiZdyrko]

Thanks!

[joshsmith]

@Banzay did you want to work on the Stripe package side of this too?

[YuriiZdyrko]

@joshsmith yes, I've already started.