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
- f1089db9dc2a2a160a9882eb6e5590626afb5a7aa118ca3194ee5964bda65de3
- request
- 3fa03926fd398346cf580da359d272c173549739142d65e49246cc4504e37502
- transaction
- 844dddf96810d2727732aaf91c61c080ef122446f3e330ea2a2f9ecc391d9654computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22326
the chainentry 22326
- sealed to the entry before
- 76fd79ea315cc3571d94f7575c3797b122618053a69178146e860ad198fb21e3
- this leaf
- 4e6e7e9e11139bffd6680b89fc5156a421466460517d6fef039377770f562a76
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ngn9fUidB9dvLIEU10CJ7QsdYswUEiMCsyzvCLMyuytOhg27ekCd5Ny4mVX/Y1Sof9eVqBOXQmOhDBdxRxfOBg==