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
- 43612a8ea0705323395de88865dedfc437e688d2ff751ba924ccb9a16f50314f
- request
- f50d944b31aa9f7724e4604298f16e3371a3cff53149a37bba8b748d15368df7
- transaction
- 4cd306a63e9268fbf622e0d1427ac3b15958ed456a15b5a8849fd266b230af58computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1053
the chainentry 1053
- sealed to the entry before
- 6ac7d08757933c78173da0f55c24f0de54031ad42b4300c00000fa561cdf3f37
- this leaf
- fad59a8b33eea91eb3d2a21b75803134a5703ab9563b85ca1420915837aeebd4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- a2+ekTOKAkyZc9y3daRP4pjXWcDW3xqX4w2UpSrY4JJ5oX7VR596RbWB0/F09kZq/tu3VBXkvGonjM13Y46FCA==