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
- bcd9cab11108da41208220a74e86dadd0a6ce55c32e61d235f967aad826b2f5a
- request
- c4ead463b8373a4be0131e5d69b842280c45c368d7bb33233d1a48bade236451
- transaction
- 224e660a2d593d9c7374cbb368d02ebe72af220df44a48bd626940d41699621fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76899
the chainentry 76899
- sealed to the entry before
- b32aec778e75fca06afba961e5a528d42f7757a282fe1a3463271be14ead1143
- this leaf
- 693df4a3e4f59e24900a4f39839527be5559563dfe9467be7667a3b8b9372518
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fCiaO6Re+y1OwefYrXhu3di6cYENkyGHqJ1Iv8txJiEPR1nQY/yah7KioThh8iOv9vDkMOTkX59JnZgY4h89DA==