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
- 1d57f6de944c03f933f18e95a0857e216d3995b8ac03a84d6d62ac4710205508
- request
- 9f686c4605652dab80d27519a65317a0cb007b1e6e54407966ce35ee084dbed6
- transaction
- 9e962fce6cbe0c80a25ccf47f09446db9a4add4867e57fe149d13979844b4e81computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64092
the chainentry 64092
- sealed to the entry before
- 9cfdd34b99a5c7fb1206ad2a702c682691cea9ea66da34d221f4cf162a9b7261
- this leaf
- 0eda31aab2c9e367c28c8b7cecbccb090179a364deb0226ec5f6c4a5000ea1cf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CAuyC5vgF6F5co45cEobimM7F8aMeGoVVarsPQzCQuBOx6CNZDwQM+ZT/SfwoaF8bpcEZ5k4OQpBUW1ONu/ADg==