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
- 9e7e68f325248c064dda4a1c8ab0342fa252975bdc0986c5f2da31145d6398ec
- request
- 2e04ea2e0e2766664a4702f6b51da30235da49b69cf65be7913126f5422eb8a2
- transaction
- a6ccfe5e5148d01323426bad278d3b90d75b744111ce8e1375267db15d0b2118computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62647
the chainentry 62647
- sealed to the entry before
- 3529ef1567589973e309c4dc43f8457086db674d9e3e97c0a511e1e4e822a438
- this leaf
- c0ccffb971b6698652e46af948e68b55bc9976550991e8eb09d601083cce1821
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sxXHuD0pegLm87eXFebXnP3FoS4WE31ppfrNS1rYCHgkPVU1LTw0KQYcyn7x20WmhRUeG7UpYH2SRUK4y0BDDA==