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
- f4a39c2bdd69d544c35bf3cb625105c49878950b31f518dba72bab3bf0674fdf
- request
- 4d3a0cdf020e01c1c67c2db6230691ad6be48d3944203a4c22813b7357372018
- transaction
- 0ebe21abd2f2f36ebbdc3ab92ed41e799ac3e219b7a6ce018f32ed09efe66ae3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53211
the chainentry 53211
- sealed to the entry before
- 1ba806bd58902da9a2b01311b47ed5ee852395c5996d3c312d95099c23426f52
- this leaf
- 80306078ae883c32595ffac5c31faf5897c7ac3826f6696e5cf59fa2a14a4daf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ghstxWUdMK8Ead5npXTc57ZDwPRtY8OC2bMjHTJO7cKLT9lQgTUoNnuV0lx+wPVHUm2dhyomueVu4TG/FmxvBg==