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
- c83b2f3a75082d03c191c4e5a6f97d9a2b4b71f3112062246ce03f9ab66a97be
- request
- 3b2a9cc4de8bdbeefac4f5918cda0e4924e340874a201ebeed39fa9014b207b2
- transaction
- e87f525156b65ff2bc3e4a8bbbfc0ad957a4718b414ee8c940ac8fae48e8306dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25610
the chainentry 25610
- sealed to the entry before
- ac92699bfd9123b20da34868ab6d41b0baf2ed0501641feaf4fe84b7d8b2c181
- this leaf
- 97e8fdd9d94617f904a668e804d3390c3145829671ff9209a06ec741bb501802
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- g1qTlAkRpt2TJji6eIH/ZZI6pB+IYEZpI0M7Rz6kzlndusaMp0wkRh1ogzvesLr5nxfWWOwtKswMihG+tTPTDw==