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
- b32d147628f6b00e9ba6549ef06ce933474aa4da03546cfdb3289c27c023eb86
- request
- 2e01bdad50c7d238ccf8d255ba16944d584e20a1e810cd040db8f0f0c1eaaf4a
- transaction
- 52ac298f96a8284937a53f754ad2e25c7e9dd26ad47fde984b8cfb1bb37b27d7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56555
the chainentry 56555
- sealed to the entry before
- e9bece836326b6c8265bccc2c9fb543d160868f258865b6932b45e9c8efbb0d2
- this leaf
- d93534e139b664876aacbee3cf806e4c0cfa75a0a898582ce26c58ff6360e05d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kN7b2+mnAor2cS+fVjFin7MBlaPD2la9sNqXx6w1wHYBoegG6MgWtR1r2QycfdpMiKsL9c/PYJsoUE46qxEqCw==