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
- f45027fd6d4f78a83b0f875f14ac31d39d9f7c9554ed46eab892e13fd4d1bbdd
- request
- 214eb2934a6fa5c94e4093fff8fabd7efd386f88da0d15e1347efa8f7ce9ad6d
- transaction
- 9559e999125bd53e7cb04af587db4155c1ebe655971f8680375a1fec3030bc69computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27642
the chainentry 27642
- sealed to the entry before
- 9be2e88b62187a14e8e8f71ea5aec546da900860c54c5593104a1aa1f9cb4af8
- this leaf
- d912494f411b0c959c87704d37348e6238708d31489eda326af38bf78fd59235
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ex7bQ2l3txlDJeyV+6ipYL2SQCdRVVV/KrvEqrLC4PiS2YeRhBdAeRyFV8r3QgBxmrSZx5Mo8O+ZT0k/TGDgDA==