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
- 7aca88bdf54f10cf9fc6eb9356f5613b1188c777c820589d9096be10fddb5e67
- request
- c594089324e41675d0a048ecd10bcc37e44c7451bf9d4f3838bc70e6afd44bc3
- transaction
- 2b84bdb370716bd78d4d3a6780770090c2e6a1afbffa240870643499218a6314computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45193
the chainentry 45193
- sealed to the entry before
- f51d5eb145b6b9f2a07db58dc5bb4f4ccf26a099bfb3871a787f50f562062c1b
- this leaf
- 11626fd16f961dd131c3c98ffd78461ce48f3c125b0a976672d71387cfd88e7c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- m9UlkRAzrb883iHOuoTJnU33IhyYzuIg7ufCnuhDSN3KqyiE2vO3zffofs8COA150iaZx52E1HQkIQc1mgKTBA==