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
- 3c53a9fcaf9aab6667a28af2b200b6c231b953ac94cdcd50c9a1ca281dad200e
- request
- ca20c9806c3d835a505b7e437fb6abe7b9b543a0f94dc81c59c4f5ce65f16baf
- transaction
- 980b9bead28831af7d006e590f4524a416ec1de24c3316bfc0cdcb6e487af211computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25990
the chainentry 25990
- sealed to the entry before
- d6aa828adf09aa31d92edaf88c2a2fe4157a200d8edee1f651507029f404f6a3
- this leaf
- 1aee6883d1d1950c91b4c54579038c97e2dc1350e34969b0401d1f63fbd47df8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bKJuri4Y6HJHUE2ujUdIBuHZK9ZwexJEmZAfi64OmFBolTy1CQ10EWLf3LF6ptn8tynTQoelXKTiepuaS+A4Cg==