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
- b4de19afa971b3bff5b88512bc94ff54a8c54ad200c8936ecce7245af50afe1e
- request
- c85f4f0cf8d35677b6e0a4dfe20e4e2bc640ac6a755043eff7995bf47d616d75
- transaction
- 7c722ab83747578a89bc19715f54c9b7af342703ebe586e8c415d65b2527feb5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 932
the chainentry 932
- sealed to the entry before
- e0ee6554ff2b3a3a363a738a524e7f90e2f04e37c17e53be85c3c1db25be9eef
- this leaf
- 57e824341c29325713257ac38938bab94d683561a89646d31cfea2b7576d902c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XxgxgsSL7evNjQ0L84VVK+r9tGCdDeKgBWHeblImvj6GGWlGOvUbrk68yEgRrNaZIcbWc1x9204/XSu+D15UDg==