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
- f6935ca21645469fb1d7a5697047ee589b93e1716619e4f51495b2baad4bac2e
- request
- 264c2c68d04ad5e80176ea28c476cefe1e9cf2ea916dd8dfacd6bc6411a3174c
- transaction
- b086ec58abfc250617fa037071acc6d09a848bf8adc147fecae0a2d2e596a699computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13252
the chainentry 13252
- sealed to the entry before
- b9e1e2cd82cbf2a6085573598030671c6c318c7a6541b890fb085fc25946cfbe
- this leaf
- d63fdcff3ecb9eac1b65f721d3539748a02077bd073f53c7c09aaff3621fc731
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WjviEAaZKW6lXnVRwzdbXacolzrTuEC+vtuXlRFlpgEGyhjJ53pMXQAjlQiAFjDAEiFDycf93M8aFk05Ngt1Dw==