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
- b57c84d7a83f21f8d8f94f5d7161790320cb712aed95ce77fd3d492d17d496b9
- request
- 9fd01960509ec7435114765ead618a0f72cb8db34fe9306414765f94627d79e8
- transaction
- 1b675cae4eace165d627f09d6b0e770209a950f6d87a268821491ab33b882aadcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 4938
the chainentry 4938
- sealed to the entry before
- 9445962c45290d1e13510d2e1cea8b68b875e42988fe2a047aee8cba0db0a3b5
- this leaf
- 42b70b6baa7c75ca400ac78d5d04f877a1944f4bbdb353eac2aba73c2930e8a8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5hZ+0RbV5xAm4RE+ZIRfUI5itXRwtcREoB0uBiZGliJgKfHuB8sv7FHOxJiiRO4zrGF9yJEzgl0Eb7b1gQrzCA==