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
- 1b177af7f503a522c3c2aadb7329741123dbe7ca2d5631db3038ae58dda8e7bf
- request
- 2793372430293711783fd7b917dd431c1bd260cb4d0c67dc96664fe3b4477c58
- transaction
- e00577f896a06e50e5ce7ebeca29548d4477dfa45af86f87fe7bd115272001facomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35311
the chainentry 35311
- sealed to the entry before
- 2fd1f76c68dcff092ac0f276e229a04e41a5affe163e16660f0b86f87b233001
- this leaf
- adb2f065704ce03356838f7dd7cca931668b1349fe1bc390318fd052313e2fa8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UUOVho8pOD2gYFoqdwOW4mM7C8yyDUPJLI0yUA1m7ejyZmsonh78to6DniqBhCntSQqfhDmfDmej5Z3CeWrrBw==