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
- b677a9ad32349a910c75421666e73349e31897491ae3eb5ff30c1a153b45abde
- request
- d5bad00ee2aa7fbaeb38af819370dee4e815993ba07c359ecd7b8341b1b11605
- transaction
- 7044d371c2494fffea4e3122648c21b79affe3fb6f4dd42ea4b925a5a03afeedcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20554
the chainentry 20554
- sealed to the entry before
- b7d1b07df99e3dee3b08ded1def42db72badc12537b1a2c579ba6ae42e21fbfe
- this leaf
- fdf51d9728a9a621bbb1cdb52e23a36d987388de09b5824502d83ac1a65ee8b5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 79lAyU04k9T5KMPpnKvHUo3q4t9bpzPxpRLNuk2sxfokm1aOnVLzW60q6QQmSTVT0JPLKd66XzCgxcAUe+BmCw==