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
- 44a0ded0bd4bb91dbb0f26d3cb8cc559a7f8d236ddafe086f3f3eaa95bdb318e
- request
- b02e6417e673c3ed3ec24ace36f78806992b3979d5b8643711926f01a6c274d9
- transaction
- 6399e1873083e383208ef0877d7c5fdedfaeb27029c5b934d1b9776ce8841434computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58458
the chainentry 58458
- sealed to the entry before
- acba988edd3021813a1fd80502b560178ad3e53693ca392562d3410e33ce090a
- this leaf
- 4511615e45e87d6e2eb82b32b97bf640aa0f5a1e5c529b6888e6a81d3279e600
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- um15bgqkpWTU+bpLSWt3drAXICTta7SR2VM+SR7IQArKghmDnKqW5CBuPToRMCWDLFaVaZyGT4hAfzvGO7L2Dw==