A place for community members to contribute product ideas and suggestions.

CIM Hosted form does not show an asterix before zip and street even though they are required fields

Status: Accepted
by on ‎01-22-2016 10:03 AM

The CIM "Add New Payment Method" hosted form does not show an asterix before billing zip and street even though they are required fields.  Card Number expiration date, and Card code are clearly indicated as required via an asterix.


This will be confusing to our customers as the credit card number and expiration date fields are clearly marked with an asterix while street and zip appear optional, yet when customers hit save, they are told that zip and street are required.


Ideally whether or not zip and street are required fields and trigger an error message should be determined from the merchant account AVS settings, or be determined by a setting indicated when requesting the hosted form token.



Status: Accepted
by Administrator Administrator
on ‎09-02-2016 02:23 PM

Hi @mkienenb,


Thanks for the Idea, you can pass in asterisk configuration when you get the form token by passing the hostedProfileBillingAddressRequired and/or hostedProfileCardCodeRequired parameters.  For more info see


Here's an example of the form when these two parameters are set:




Let us know if this is what you were looking for and thanks again for the feedback,



on ‎09-02-2016 02:38 PM

No, I tried setting hostedProfileBillingAddressRequired=true when it was first made available (and I just tried it again a minute ago just in case the behavior had changed).   When you use the hostedProfileBillingAddressRequired=true  setting, *EVERYTHING* in the billing section is required.   I only want the fields minimally required to be required.   The only fields which are required for our current production settings are street and zip code, due to AVS.


Basically, if the form requires a field, indicate it.   If not, don't :)  And having the end-developer (me) try to guess what fields the merchant account is going to require is always going to be a losing value since the merchant may change that configuration at any time.


by Administrator Administrator
on ‎09-02-2016 02:48 PM

OK, got it.  We originally decoupled these in CIM because what you must collect for card-on-file is not always the same as what is set by merchant account for transactions (for example some merchants only collect CVV at time of charging, so it's required for payment transaction but not for saving card) but I totally understand that you cannot expect to stay in sync when the fields would be the same.   This is a good suggestion so we'll definitely consider for future release.





by Administrator Administrator
on ‎09-05-2016 11:34 AM
Status changed to: Under Review
by Administrator Administrator
on ‎02-14-2017 09:24 AM
Status changed to: Accepted
‎06-29-2018 08:49 AM - edited ‎06-29-2018 08:49 AM

New to the community. Any update on this item? It is a year old from the "Accepted" date. Is there maybe another place than this board to track status once accepted?

by Administrator Administrator
on ‎06-29-2018 08:56 AM

No definite dates right now for this feature.  Thanks for checking in.