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
- 37fcc08f133a63cb80dac5151bcb5e508df2f385342403b9c0a7fae327a09fd8
- request
- 6fda5070138d1cf11311acb441ab662347f6079ba91368bf42d9a87e99c075bd
- transaction
- bf98effcceb663b953589e66cc3c8e1d6553a7797972ec2a09f8346f9882049acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20933
the chainentry 20933
- sealed to the entry before
- 8300a5b8dca8212ac2987f487ff59f654078b71e2bcf1f7d28d710f86fd236df
- this leaf
- 35768ccb00e6b7d21d53628033ec0eb615f26b0c2d3cd5d30a489de0fa38a900
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- L48izUvUKPDhN+TULaJUbKYnYnj79OBiXL+uyU+sYNKejrhBfnjtiYPvrXdkiac54TONL72VZ0HyIfUbIoz1AA==