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
- 468951d52da5211954db2f8966c988e66ccb9c14fede3d35b18b630218e1dfc0
- request
- 02bdbdd54cec770eb41e46df1dbbbe8024e0ced46f3be7b2ed2c0c104468be92
- transaction
- 3e7c54bc6724dceb7ff70071e930d4df4269a04c96c35a8cca10d3ee23d94117computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62083
the chainentry 62083
- sealed to the entry before
- 4776078201076e9010641cc3831da05fb70baa41c90ec12afa685a053550a458
- this leaf
- aa2072ef7959512900ae76a5dece73d175d984610eb7461cc1fab3d0883321d8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hmqEbmV3zSgqLefSVpuvIB77I+EuzA8cMlRaCGWtsLRG0f+C/l5RubxvV0K34cXPcZSQpwKW1/uU/85Q3OqfAA==