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
- 5d66ec423a40870a0c1d169b578ec970cae72c1036abe252dec8dbc0d8cd368f
- request
- 89cf4f77a808ec549ea41af653f1b08059c97f8cb49a15bfc9327ffa861ba007
- transaction
- 5a1445da086c92272e486222cc6530ad4d3e488000a94d223094fe9eafd15486computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31215
the chainentry 31215
- sealed to the entry before
- 0f0ce19345d18068122f73f46b4a3e10c688c274d505929ecb8ae23eba7a43b2
- this leaf
- 303919e3dfa05e8851622b62ad65a2b5ffcd108353000b695779463b4cb58281
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gNACCtZMXxgSkWGiSHHWQgjLN06/ZN49KtqgJ4G7gKabknjJyrWh4tIl5hq9W+SjSQen7//ywYrKV23xA2UECw==