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
- bcde82d9dff391164812c52455e7c961f9631dd56a3282a64c48f80e056dbcfa
- request
- 510d135fb00cbcbae5835afb5728bce5a6d542f27e5f0ca795eb3d6c30f57ff4
- transaction
- ca6c1988b13857d313a6440036add8e52bf6c771c5b126fd91afbfb5650e403dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8033
the chainentry 8033
- sealed to the entry before
- cc421cea4fe46c89a7b56e75384ebf288b6f61c3c54dde57c93b9f0ae525c3b2
- this leaf
- bdff3b1a61882c2c09aab399e29b611f7cdb365ede33e286eb35334369c31ce7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RuDiC2wOlRK23kH8wGYLNhuFFCMmVbDL7pAvIYmbHL5eUToB7OP49w5mLERVFq041Yvf6s6j9CAN4PG6+lxIAg==