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
- 3bfe9e0f027f6eb34fad91ba565a003a87cd3ed8a2dd342c0253b135db5a667e
- request
- e37aed840b76e145365f2178479169b104e66f68fc27e102afc0cbe13b349c5b
- transaction
- 66b4261d78bfe5e7935062abb524e6a350ae5cdb02410b6c6095239c8413da06computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20193
the chainentry 20193
- sealed to the entry before
- 7ef2f4efb7a3f9bdde3dab7929e95436b30769270f30294ff02d975190049e19
- this leaf
- a668b39d39f1be3f19e7a5b3a393a6f394116847fa4b2708d0c185a29b9243a7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- z66LjjC0mprO73rKK1nGlnlpVAtMdx4qTARenbt/oGjiY4dyJGJw4toP3ojPPnTZsJhMSD+IhxRXBrFPSu1dCg==