Relationship issues *should be easy but...

[skingjack2]

Hi,

This question is an extension of a different query posed & answered in another forum (http://fmforums.com/forum/showpost.php?post/336661/). What I'm attempting to do is be able to assign a specific credit card that was used for payment for a service when a client has more than 1 credit card on file. The files (client_data & credit_card) are related based on client_id. When choosing the appropriate credit card ID (configured to be a drop down list showing credit card type/issuer) it shows the appropriate cards for the client however I am unable to figure out why the related fields (i.e. credit card number/security code) are not showing appropriately. This should be easy but not tonight...anyone up to providing some enlightenment as to what maybe awry? Suggestions muchly appreciated!

Jack

[Simon K]

It should indeed be simple - if they are linked on a client id (do check that the customer selected did indeed have some credit cards) - Do also check that you the link is indeed on id in both sides of the relationship - also check that the drop down list is is using the id as the first field and the credit card as the second (only show second will work better with a pop up)

BUT - you have a much bigger issue ...

and I certainly don't want to teach you your own business...

under PCI-DSS rules nobody is allowed to store the security code - at all - not even if you believe you can store card holder data by complying with PCI rules

So maybe a rethink on what you are storing and what you are using it for - if the idea is to recharge you would be much better using one of the "token" based system from an approved intermediary (even they don't store the sec code though)

hope this helps

PS - up to now PCI-DSS rules have been perceived as only applying to larger co's - but the reality is that the "credit card" cos are being much more aggresive now - and progressively seeking to apply the rules to smaller cos

[skingjack2]

Simon,

Thanks for the response (particularly the part with respect to the PCI-DSS compliance; compliance document has now been dl'd and reviewed. Fyi, as the business has very few customers for now, it was no issue to delete the security code field & all references from all the backups to ensure compliance).

Re: original problem...it unfortunately still exists. Noting odd behaviour...to test,every time

I choose another credit card via the popup list (was drop down)... the new choice assumes the card id of another existing card (so now I have

2 cards in the credit card table with same ID). Not good...obvious relationship issue. =(

Jack

[skingjack2]

Very happy to say I finally was able to solve the problem...after reviewing an invoice example I was able to determine my t/o was incorrect.

Now onto the next problem...

Thanks Simon for your suggestions.

Jack