From https://civicrm.stackexchange.com/questions/28250/drupal-webform-billing...

On Membership payment, using Drupal Webform, someone living in Singapore (for example) can not pay, as State/Province is required and Singapore has no State/Province defined. Gibraltar has the same.

This seems to be new after a civicrm update. The native civicrm contribution pages show state/province as a required field, but on countries where there are not state/provinces, payment will continue without state/province.

CommentFileSizeAuthor
webform-after.png25.17 KBcommonpike
civicrm-after.png26.67 KBcommonpike
civicrm-before.png84.53 KBcommonpike
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

commonpike created an issue. See original summary.

commonpike’s picture

commonpike CreditAttribution: commonpike commented
Title: Payment form fails in all countries without a state » Payment form fails in all countries without states/provinces
commonpike’s picture

commonpike CreditAttribution: commonpike commented

I've now added the province singapore to the country singapore. But that only helps singapore, not all the other countries, and I think we shouldn't be polluting our database just because the software broke ...

again, this is new, it didn't happen in CiviCRM 5.7CiviCRM 4.7

KarinG’s picture

KarinG
Location 🇨🇦
CreditAttribution: KarinG commented

Do you know what the exact versions of CiviCRM were before (when things were working) and after upgrade?

commonpike’s picture

commonpike CreditAttribution: commonpike commented

Hm, ok, that seemed wrong info from my part, sorry.
We upgraded from 4.7.31 to 5.8.1 - so quite a jump.

commonpike’s picture

commonpike CreditAttribution: commonpike commented

I ran into this again for North Macedonia, which has no provinces, so members can't pay.

On Stackexchange, KarinG wrote in a comment

The billing fields get pulled onto the webform as-is from CiviCRM.
CiviCRM makes them required - as some payment processors based
on people’s merchant account settings run address verifications to
limit fraudulent transactions.

but it seems CiviCRM itself is a bit smarter, it does not make the field
required in payment forms if there are no provinces.

There are much more countries that have no provinces or when
provinces are missing. The list is installed when installing civicrm,
it comes from ISO 3166 and ISO 3166-2, but it gets outdated over time.
Here is a list of ~25 problems from an installation in 2016:

https://civicrm.stackexchange.com/questions/11133/adding-states-to-count...