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
- 6c11bc3584b26db8a3dac8dfa6f7de1d111ecafe2cf25f687ce8ffe99841f209
- request
- b98ba86d1014b720976fbd9d71a71f14103800830f1d5d722610920bb4f28253
- transaction
- 30d451b41147e31822c55c33117826306ec6d175e07b00947d7bb6e7a4f0c755computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55640
the chainentry 55640
- sealed to the entry before
- 5e4a97478b59809f43f7a61590b04cda770d84b43e24f701f445df1721b4a694
- this leaf
- 30efde98d7eb32ccc2f09cee15b9807eba16bc48d476876747def8acb4641444
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7I2xQx2ckH+1arrGseQNCMZBdEynRHJttXmglmbYCE6u7GJUNShlQ4AuoHc1nQ7p4BVNEHPP7chQY5g1cJxrAQ==