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
- 3349a47002a5c16cca5e6655f559ac6d5d8fd9d898402403352ceb70cfc3dae8
- request
- 82178fa42d82080e637ac13d0dc74161c08b2584dc121c4d8c9ef32bbe08c9cd
- transaction
- fa59b515a44dde31c5eb333dc3c5b89f4cd3452163861aa76ab5939ad058ff42computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2962
the chainentry 2962
- sealed to the entry before
- c43faaa1251a20f8b2a0b98cfe8314cb415e80d073cf3e162054eab574f6ccab
- this leaf
- a4071d9eff1b51f238b93d57794c2737573ed2810d820be8e95bacc1289c3fdb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +VOXDQu0L9W0Z0r70al//W4MMZKoUnbvdtkqpeGT1zszTH0QHemtLUsNP/MvalVe5RR6qZnH/5UGZjpM/oLTAA==