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
- 3572d03257735922634f451c3f61eb81d4ac07999b2f6dc7aa5141dc25870c02
- request
- 96d50667fd27a2204049cd0cc7ec288c403d9015b8b98ac94652a58a9f0bfd11
- transaction
- ed801d163f7c5193f261ee66f4490759270d1e95c86d7811604fa12bc3aeea9dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22223
the chainentry 22223
- sealed to the entry before
- 7c6b12b92bb801831e4a67a297712305e9a4db24b71408450e0b47c55cbe5ddc
- this leaf
- 8a5f1f73bd78a2cbcfc51c0f83efe933fb7ac9df7996eb8364b34d389d529b59
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Q/9PIN3AWlEAhxhB8sa5MRDd1xQCq7KboF0aoG4O/B2Wh2y+gJaYocC+odA2BtlA9ozwlscjngbBRRPYCsIaBg==