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
- 7f3a4cc3b348079fd07f4a7a6e4df233bec05d69347ec6bfcf2c20999b11dbbd
- request
- 4650544f5bbda63e0577362497e44382a65c1d587d371de1c6a067acacf6ada7
- transaction
- e08141131983814d5892b351a528fe567f59c35e75eba896567ad5e1d2bd16facomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27413
the chainentry 27413
- sealed to the entry before
- 3ae75fd15360fd7b2f0c752189fcffadaf5e78f502676538c15a1b1d388a6f8a
- this leaf
- 7df77bd7bf6a8c660d5f90473baab3363e9156ddafc1de1a29be9a59dff4fea4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MP54j1E/KG2nCs0QrHJJTprXaTR4ZNiLOJq1aquVO0ri/8Yk0Psw0rcdOMH3/bcv0T+WAKVx0233EVGbM+cyCg==