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
- a00daa66bfb53ff257288b086217bc3097876df9cfe4d2bcdcf37c2d336ddef8
- request
- e08eda73d1ec45758c53af4813e35730d9db18ca2f9ea4d788d0f184c3c9dce0
- transaction
- 4ee9b49ff52f6534faf62e615acf32b3656b85a72fd646b86b730c8db7e552d9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9158
the chainentry 9158
- sealed to the entry before
- c6330cce1dc16144931a2caee1a9966307d05df490f104a99c3eee3931545ebc
- this leaf
- e2b50e79b45df0940a701979d03931b498ffd90a6e34c584bd78df7823a7c5cd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UN3IgnYZaAwFOxf6x8w57odHaeAKkrz5zwWGJd8iDSA5755xEGYuIZZwgHQ7V8vJe48v9DEwGXz+jG/hpEQVBQ==