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
- 1ee4d8979300a59ae8aaf3d6dc65aa69b502a35db44706d1cb664ba8afa0b30a
- request
- 94fcec55e39f46d83bbebc2f397d74d8e81783e48f506d9ba11acb1d2f246be7
- transaction
- 32c63be8618adfa4e7789a64014c9e182e3b2f69a1b2d1595ea0c2ea0affe45fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 826
the chainentry 826
- sealed to the entry before
- d515a1abdac0c53fc4aa2d389c3f03f3e633f11fd96a654867594bbc5d4618e2
- this leaf
- 7de217bae9bdb5eaab06268f3718e0a9a3517760d9495e421006de5b5a2739a1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sm74VcOn6LMQwPHJOcGZxmvlh+H1Hrfri5d8D4dvVXUq8H3xlQZvAWdZ0f9VFCj9AE/9g9bmH87X3FECFpTBDA==