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
- b7c1676655246351faa7a80dfd1dbd19ccd4a02a34d0a49640dd1fcad33e76a0
- request
- f20a206be492dceb251acf4cc97215f4a172d1f500e87334dcb819e05e61fded
- transaction
- 29a162a3aa1276375a675d4286233a98ff9bd56386dd91a926fd9cfb5116e798computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10652
the chainentry 10652
- sealed to the entry before
- a413b24d5c7ef079273c763021b03ed22e5831066beb886b75249fd16107e5b0
- this leaf
- 12983a6199b110a03776685644cd026870c23d6ca97582f7f759e30213176130
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LbB8vkVubL7ZLw1ybpZtKKuslIQpzqE1w0EZryrxfe8XwrXhcGXXygahKeOYvgMfNAMr+4A9EyGU4dWR2L7HDw==