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
- 4b3136b5e36b1c03ea5fb466f2745097f8c7dd5e362389d41182d8b5002da1ec
- request
- f037f3865530a284022b7b33f60879ac6203668d40482cefbe7d8e5020fa2bcd
- transaction
- 141cd8d7f83783d36d406f1626220223d86de56bd56f799d6c82c5b007a6c505computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60762
the chainentry 60762
- sealed to the entry before
- 5ac326a66b0f0afd769c6692dbc518dfb14572b560b3dbb51005f56341978893
- this leaf
- 8b95125b48c8445efc4aa25ce280aa4ad87007ea9c5408fa22610667fb52e3eb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UJLPR1BfeLprEpoDWAldT3dDKGsnl9iH3RP/43OFM1GiegCR1Dez42zKC2gPEp5TfHpRE8W3gP4NVdWetCZrAA==