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
- 34369a603f901c0be6ba344411557be5b1fdaa5d8f2762a4e99507b7996c0132
- request
- 4bf898bcb6669d358cb8437000767b233c42d86641d8adc137b6b266b95e35c7
- transaction
- 9f5f0d592bd18af363c02a1a45890d5b03a4d302cd40fb953a2c234fefb63118computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44069
the chainentry 44069
- sealed to the entry before
- 74522efc0fc4d420f561ed03e0e930431c769329b4bc88109a8bddf6e04a76b6
- this leaf
- 71149d047a592831b511da42607834cfed42f7c940813822f5024eb3cd0e2bb0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jWaei4eX2NvDFQW4T9QlWSVnxVZJtojpmx+hISnxssu4uW8a3BgqwUzui8HJe3yBY0CHAyIgyBgmLLzrQE2zCg==