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
- 70aa2a15fdd2c71956e565426f08f5e007ca73743e142848e7c0c996cd59e332
- request
- a345b87cff0d6867a81901b7aef5bcd7580ab4101a798efc4061b7212e8d81d9
- transaction
- fdb00dcd57bbdd15fac70f28a404d3b10c62da3d54fc54047a1cf893f6df3386computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28099
the chainentry 28099
- sealed to the entry before
- b90c9a8acab241bcee9dfd74faef00d1c1ccdccc5bed516c25e98c7427960eb8
- this leaf
- 92d5f084fade82933faf3ad69d4854682f6b5ae08d3f085c37fe15537e1d8bc9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- baXkkXQya4gamyyVErhI2yLCsxEQVBGzpyHW5wzNNINk5AFZ5GGigFXMK1iQiqmMHKCCO2RrlXLceloRUVSaCg==