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
- 57f881692ef35f06cf60c90c67ea8deb85e5a3673f90894dc314c2ded7206e14
- request
- 2a11907768cd11fd5e71e6fa7e49eb17bbfbfc4680f263d94005a73d00118fb7
- transaction
- 037f1ff36d9d4eaf0531a7c03a516204455b8983a1df30d8591eb8e45d476e0ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53840
the chainentry 53840
- sealed to the entry before
- b7e67e3bb591f747177ebc199a71aa97ce8f65ced1814844a20d6756f298110a
- this leaf
- 3216e0a51e51f68dae442f9198bd893f840e184c4ce26fd1eb18dc1cb5618e63
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Bff/1lCBLiViqekzcgsAY+8U58DrykuEKQiSt/IxCBAPluA1zEAl6D2PHxSbvK92cfrwVlFkz4jPNST5mNESCw==