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
- fdcdb9fca2a6b0d6a4d2374023fe8de97f297307888a79d9126bc7377a7b72fb
- request
- d0bf5da78cae315e9542bd6ba43a08ee653208bd432a2eb6b5a41d76dda84f66
- transaction
- 38fa5a18be3cc4699e41a637022fcff968808a1e0dacd166266434a14dc11573computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16607
the chainentry 16607
- sealed to the entry before
- a3965a3b42167d85d7008dfee247d105490d6b60c610a69d5aabc761479e5945
- this leaf
- c356afbc346fee550ed532fe82a7d763b030184c1c0d2232506d09014925a74f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- p3ue2ymWId+rcxhNolmBi943GM7BJea+vYQYetsmrlkEoqjNcSyzNbJLiw3k7tvSLEeNt1AI5KBZy+VaptAhBg==