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
- 5ffcff54e493f030f0955f9b651d248b92fcab0fd8edd8b921140550a834960c
- request
- f4632c0c806835c4851b9e2391b7ac86db41dc37f590054c87101e51514459b1
- transaction
- 13e52fac1b7715256434cf91a1409426397406e3b2c101fe17852bd109eae6f7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25584
the chainentry 25584
- sealed to the entry before
- 906272304d57871875536eaed0c9027101831335360540b7b03cd960d985ff55
- this leaf
- 8c3ff7bac2dcc38eecad5257272a9da04001dda1c6e4786ab391888ba522d608
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +484Z/RQVZE8BH80lkF/M6To8HHN1E7GtndocUyWr3QBd26RVmkeAOamNbV9BzVI5x7pVs0XtC4Huu7kiRNwCg==