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
- 06a8c0a4dd21f983a56da45f18e2692d36088ea20cbc64f5d8cbee09a60a5947
- request
- bd8b8cdf2e116e206d898342e62d0558b667546653fef5f6db385e1debaa5802
- transaction
- b659817c1b45e1e4296587fce1123533a54d43fd8ffb2714ae047b79fe5126d7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68992
the chainentry 68992
- sealed to the entry before
- f45f1a0a85d5ff03e043d443faa4aaadf4ea8a3bafc4d0d35ce8435bdfd837d7
- this leaf
- 9389665565f490b8fe6bc2dd7a07c84965ee2bfcdb79340ea9265b719022a85f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bPbsXN7YGtlSvCvp4Qr3/kTq87tX7gONWdHQvwsvsXjag1CG6XfMDMuCcr6QW2sR/ahVUrzaZ8sZMY1zThC0Aw==