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
- 9ef72e41cd089ebd7ff5cb29b914dd22cadc89acfd0b72e7fbd5514a909d816e
- request
- 0f92dadab0d064f70375e8a77514d0b29ea81b90b02d95113b0805c8ab199408
- transaction
- 3dbe6b55261a542cc870701e15ca551d5fd3810ee1e70753ded00e8a6062a357computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75715
the chainentry 75715
- sealed to the entry before
- 4bed6d8d6d7a32c2e76ca5a4e62e6598483440dbd52b1cf4eb500867d4d171e4
- this leaf
- c076a3bc60876de2cec6c591f05f0988024b11c1fad8aab36699d9bd3199f6d8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9XM/RL6UgbgXv1439w00Xm27irHzwLN6ic947RiJztk+M7Etm0u+tbCTjb0YQsjxdb55jxExoFQPQsbMR9gTAg==