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
- f4cc859f95c02d56c7c182cb2586115447566d87e5662cd75865b41eca83d347
- request
- 110b68d7d31bb051d0d5e5083bdc2ec8783d1c91891d9d229b006d35f59d25fc
- transaction
- 06082723cd049dd9461ee1245e04960e336d2a428cfce23884e519ace0d851accomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54060
the chainentry 54060
- sealed to the entry before
- 2ee7799ad25cb4d93a8833c958716492f6e379276197829a6a0d06821355dd6f
- this leaf
- ad26cdc12a87ce1e7979701e249cf6eeb008cf061885f28f15bb1afa07f279d6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KQLW8Jy36y5TyWaK9AfYiB9zMoGI3eItU3awMklzpOGUcqNPbJ4gaOLqgp6IDro/ZW5mAuEHjevaJSeAzUxTDg==