You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was looking to add a PR to support an encrypted card number in the PayTrace gateway to stay out of scope in PCI compliance. PayTrace has a JS ClientSide Encryption Library, more info.
But looking at the Activemerchant Credit Card object:
#number strips away characters leaving only numbers. (see file)
#track_data doesn't strip the value's content but doesn't hold a meaningful name for a crypted number.
So I'm thinking of adding attr_accessor :encrypted_number to active_merchant billing credit card object but wanted to get some thoughts on this before adding a change request or if anyone has a better solution.
Thoughts?
The text was updated successfully, but these errors were encountered:
To provide a cleaner slate for the maintenance of the library, this PR/Issue is being labeled stale after 60 days without activity. It will be closed in 14 days unless you comment with an update regarding its applicability to the current build. Thank you!
I was looking to add a PR to support an encrypted card number in the PayTrace gateway to stay out of scope in PCI compliance. PayTrace has a JS ClientSide Encryption Library, more info.
But looking at the Activemerchant Credit Card object:
#number
strips away characters leaving only numbers. (see file)#track_data
doesn't strip the value's content but doesn't hold a meaningful name for a crypted number.So I'm thinking of adding
attr_accessor :encrypted_number
to active_merchant billing credit card object but wanted to get some thoughts on this before adding a change request or if anyone has a better solution.Thoughts?
The text was updated successfully, but these errors were encountered: