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
- c99fb979fbcaa25f643f9e36d90f20692e9e846bcac34129929a9f4fe961bd95
- request
- a47447c73e2d17ab3fb85805d2e417ede58d74c4d953b5026e30856b13c90aa4
- transaction
- 5c124c8f27c6604f3edb554cd08ea0ba54ab1869bc4e947b29e4239026cc7fdccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16147
the chainentry 16147
- sealed to the entry before
- fb9ac734c49db09a8a9ef74ec8b5364c0e845cad345e1374d654d399880cd4f4
- this leaf
- 7a32f904babb8576af10b8bbba0d2c57d8c1115ee2f0479566123b6211f6cb6e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- X0AsQbtFZ+zWutjNN32CCkmiyQRKPhA6AcDFxYvqjQ1Z1/KHyV0TZhn6pbtlcm0ZPLjc4O+1+9DLrajPBAX6AA==