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
- ccc737c9d278f6693270b91a15bf1481049c9289811c67e353a003ba70e08600
- request
- 8710d1f17a874b1cb6996133d239d7678e837496aa764fdd52368b3820d3d693
- transaction
- d797c885105aca0c59485198b52af3e9af60808de5443889857b23b6aa5eab79computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60678
the chainentry 60678
- sealed to the entry before
- e7d95852ca68bf70e20df74f75f0040acbfc25c7f417b0b9093493eb1726ca92
- this leaf
- 6600a04cd682625bf02df27984cb86fa3ea1da2907860719dda4918522079f4c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- v0l0cFDpoV/nFZLbjWi3oVMGYlPzCbGUOI1b451cf43OCt9vWD+rjCihTvKYZsUiMyeVcOpP5LWL/LUKL958Ag==