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
- fdc12c3c76bb7a347f982cccecd45c1883b5049e98353a69f1947f362d1200ea
- request
- bfe76d2cc52455fd2e77f0c2aa9843fc003ded8ebc8b979a6b8b55b31598b5ee
- transaction
- c52823a8f644ac1eb5011fbfc15057876147fe9f5163040b0fef2fe2536baae7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51336
the chainentry 51336
- sealed to the entry before
- 3e0f75d89e512bdd733b06d0ec5c29fc27b168b2da087970e3d7009ae005f93c
- this leaf
- f07a94d0a459e95a9888074cdbdfe9f2ea4ce7fcd88380c43e634928df41c05b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +v69JYu077IVV1UrD0GhKQT+oomfSSkXc6oL+nON7l8TYlGH+sP0AcRswzi+kqA9Hm5P4/hrKdWdIt8+F6meDg==