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
- d09745249796a995f2b717872425f3f059359433a525e4fdeafe9b02d969de19
- request
- c3a163730c56b3e695bb0a6bff58716566140fdf1746879ebcf94b9a4cc6e3eb
- transaction
- 6e91197d1bc538c2e0a2b89f5be10a5973793dbc010a020d018c2d1e6feeb709computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74587
the chainentry 74587
- sealed to the entry before
- da4beb51f0e3944dacd352f378b8db9000e17229de2f7a952dbb1defd7b9ebe8
- this leaf
- 65893c7d796b82159e5a598494202392b84d3b80c002d21f0334af7da3e257c7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BkFNOcS64pfcW06jwL8d88ocA6ko1lR8Nndm00JVJaxcUa03Z2V2uuql5Ru7EMXBY5Erw20JwypWyuDkP6zvAA==