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
- 3ce47a960289f2610257c84b8d695f1412026ddb9a6e5bbc95c3ae18613d8d56
- request
- 44d3d66aca9b11c1affcefaa4448610b1c80ff5346763405fd3727e8d737c70d
- transaction
- 393bb5c94b6f60457f2f05b7cc3d2705fac904fd01b2f52232c586926520a9fecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21150
the chainentry 21150
- sealed to the entry before
- 08b909d1e3213e0dbaf1eb2caeddf2f2df948a53882031c61ab2c7463bbdf64d
- this leaf
- f17fe10bb60add0aafe9bbb55c46980c33a040cb666b5726fac43d4cf53aaf16
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pDOjXJs4QFU5lHJ5ZbKZJOdZujIwdCiBZnH+K1eSOpTwvgl3uUo35SUgsNAb24KtL6PKMMHzQ1K8vXJPeETiDg==