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
- 84683615a85c08e2005c6b279ebe2ad9fb664a11919ac2c92824b121bcbd900b
- request
- a88b7a4e17304a7548567fccbf32e321636b6fc176bcd809554588b8e83a607f
- transaction
- 187a13d4e244ff5115701139bf2fb69b69a7b5907a349ea4d11722f25abaa882computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 4321
the chainentry 4321
- sealed to the entry before
- c5dcede21695ad8be815f53df446bbee0d40a5140008a9c7935dda57f2ad2910
- this leaf
- ff3f1725b0c0e0da760a3f4d55edfe336206ffd2a2181cca270e756076f35c03
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tQXDY0j4mGVcjtxpzf7LhlzWW9hDXhhK9lxarsKj4jeOgA11kYlU/hSI3iYbwvzomEeBn8NfiZw9wF854kbeCw==