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
- 217ce385f70a0ce38c5096d2fe6e20fc5e598f506fed68bcd159310be457f22d
- request
- 9b3269be67d40d96c37765fbf07c987b563a4e9f41d710042926714103b7c9ad
- transaction
- 337e1d01699ba5b11d79dadd421ad54cb922ce7e8ea049729248c81f7e39ac42computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56405
the chainentry 56405
- sealed to the entry before
- 8bc162ad5a60ba371bdc158b5af92c97e236e57e7ad8502bb7ac53ab0809c5fe
- this leaf
- b2c4db1afa21b936a6992c086d738b51c45de9d67275966840e0c03611bebcea
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- S4TU0goUqGFcWE47E5/sr1cekPQUpxGfC02s1mEeFHn5RUbYJekeS3yWTnVc0Kk2NuedydJfl69cuxRdACW0Ag==