Clarification needed for Controller Object for non-US resident

Hi,

I am trying to follow along with the documentation here: Business Verified Customers | Dwolla API Documentation

It seems for the controller, the stateProvince region and country is mandatory. While the country is a two-digit ISO code, the stateProvince is

Two-letter US state or territory abbreviation code of controller’s physical address. For two-letter abbreviation reference, check out the US Postal Service guide.

Can you tell me a sample payload for a controller outside US? (example India) (can ignore the other dummy values, only postalCode, stateProvince and country to be seen)

:controller => {
  :firstName => 'John',
  :lastName => 'Controller',
  :title => 'CEO',
  :dateOfBirth => '1980-01-31',
  :passport => {
     :number => 'ZA1234'
     :country => 'IN',
   }
  :address => {
    :address1 => '1749 18th st',
    :address2 => 'apt 12',
    :city => 'Des Moines',
    :stateProvinceRegion => ???,  (which stateProvince should be given?)
    :postalCode => ???, (if outside US, example India, postalcode is 6 digits)
    :country => 'IN',
  }
}

Please help me with this clarification.

Thanks and Regards,
Sulove

1 Like

Hi @bistasulove

  • For the two-letter abbreviation of the statProvinceRegion field you can check out this doc for reference - https://en.wikipedia.org/wiki/ISO_3166-1
  • postalCode is an optional field for non-US persons, so it may be omitted.

Here’s an example for a controller whose address is in Andhra Pradesh:

:stateProvinceRegion => 'AP', 
:country => 'IN',
1 Like

Hi @shreya,

Like @bistasulove I struggle to create some non-resident Controller within a Business VCR flow.

I use built-in components, however even I try to use the info you provide here it does not work: “State or Province” remains invalid.
I tried “AP” or “IN-AP” (as seen on ISO 3166-2:IN - Wikipedia)

See attached screens.
Thanks

Screen when trying “AP”:

Hi @vince – thanks for reporting this and for the screenshots! Looks like there’s a bug in the field validation. I have notified out team and we will be working on a fix! I’ll let you know as soon we’ve rolled it out!

Are you testing in Sandbox or were you running into this in Production?

Hi @shreya ,
The tests are made in sandbox, with built-in components integrated within an app that I’m developing.

Same issue occurs when doing some tests with examples cloned from Github repo GitHub - Dwolla/drop-ins-examples: Example Express app for Dwolla Drop-in Components.

Please note I use client SDK v2.1.3 in my app (https://cdn.dwolla.com/v2.1.3/dwolla-web.js)

Hi @vince – thanks for that info! I’ve relayed it back to the team!

Hi @vince – our dev team pushed up a fix for this last night. Would you be able to give it a go when you get a chance and let us know if you run into any issues?

Hi @shreya,
Do you mean the fix was pushed on https://cdn.dwolla.com/v2/dwolla-web.js ?
It seems it’s ok since I was able to add a non-US resident controller through the Drop-in components examples GitHub - Dwolla/drop-ins-examples: Example Express app for Dwolla Drop-in Components.

I’ll test in my app today.

Thank you very much.

2 Likes

Hi Vince! I believe the fix was pushed to v2.1.4 (which is the latest version; we’re still working on documenting the versions).

Yeah, let us know what you find during your tests!