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
- fa631536623e35501974681d573c57fcd5436d39337490568caadf04ca3108a1
- request
- ce859250362897646074cca49f911a9d3d93897664ab5a9854dcbcb02f24486d
- transaction
- fc3361cf2ba64874c013d428355db3b5e93204c90baa80431a9efd429a592e7ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50274
the chainentry 50274
- sealed to the entry before
- d6a488b02227e3baf3279ccbde28caeb5deb3eb8e52e2724347e27fd25627443
- this leaf
- ef1c35c2c0efe5e3f245f75c8ae075b7d46b8d0d2512d0277ef1c6ffe5115a03
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- L3Dk/vk6ddJelmTFTlRagFWjaIwELqneshqsc1feBGrSOfbQvWk0DKLhM7HxY/hiK3vqkHYTj34GQI2BE5r2CQ==