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
- 8cdc462c1e63f7062a6800b3a6baf59c673fd75c439cf241b9e62c61365de1ec
- request
- f3460ea4f27afb5d88d6fab97b63135afe2c585aaf4dd769177243e5035ce6fc
- transaction
- 6cbf51be0748d5e874bedec72030a19a136e66cbec81cccf2109948ea1ae1241computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26391
the chainentry 26391
- sealed to the entry before
- 1f2a1a7b57fb4f73dc13d95fdcd72678af114c9769f520043c4dacd44fd2f22c
- this leaf
- ba52db9d6c7265676bbcc5d68224e1d59d9d033e719aefbef30d4046fd97b046
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fawsJ9iDPBBBLfmPcY69vFwocugTgpuYzZi22MKUsBNsAdT7Cpv14bJii4yMwGG4BDvbW5V11ws4Z/oowELTCw==