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
- ebed64f51198ba6f8984dbeece6eab17bfac45178ac269394afa9c376ee4ee80
- request
- 7168e2e79b7e85728998068fa164061b320b2d4087f642a1de2e00fc7f1b543d
- transaction
- 6a154ccf3da7279e843354baa45f9dcbf9186f08642acaa2f7cf7968c35ef445computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 636
the chainentry 636
- sealed to the entry before
- 5079c886d928ee4a57443170a5b295011292b66e314e44b9a101f15c66a35402
- this leaf
- 155747e90340f4c00943f6241172611ed3d8737eb1cfbfbe8d32113a5c1c5ef7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SlaZby5vIa2ackA4hplV2suh7RP+TTR/NpzIXSGlm2cP5UDfh1s9SSunRUJwEYsY7e5GAJJcSVHXmODlCkwjBw==