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
- e36dd26fad22b8e42336859c246cd823021d28db6abce1f01b77eed7910a79f6
- request
- 85e19e8559e82d64cfbd2fca9a67d7abd9ad8a468c5d5166409020b019cd1c0b
- transaction
- a0f227eae064d8a361bc00f7499603d1ced76ed89dab46499f9d60c3f581b87bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22744
the chainentry 22744
- sealed to the entry before
- 9983042242c97550e3fb4621ff5751095c1310c5a749d23d2c779c791398639f
- this leaf
- b05ed40c07b2d528cc1407ecebacf158e247a8ad537d51f34660139ea46c0086
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mE5/fGkTVWMrjHxg4+Bs5EE8srre1SsL0MXMhiteOxudnSL2Ad4wP5pB0AbeYGge5aSk8mbWzbd7gDKMf5MkDA==