why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- a842eaac10a7e36a41eabf8ba6754bbf7664fc693a7993f270b33786c04aa981
- request
- 6e8293aa68fa010fec2f3cdf6d6e0f9b61173fe1fc22f285571e40ceeec89123
- transaction
- f836557090c6f368363f491c0a0875b9c8d495125c1676058f4cafc012b5645fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52218
the chainentry 52218
- sealed to the entry before
- eeb539ba44f1c7479549905f47fdfd2fe7928cf101507b358660f091c1712370
- this leaf
- 87345eb95f78a30b38e6c776946fcccdc3f46be91c007a6889186103f6da5d7b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AmK9LkkRoE415rvS+TBDswMYmyfdU7LJTcGCx+Dc6BCrxvSdOfkt84hog4CUhHtReFdJIkGZav5z9kasO/5DAQ==