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
- 1c105d4c25373081834d681c03e2ac71713e5e5b70e017efa9d75ba8484cf6c3
- request
- c3a98d2ebf66bb4d498d38bfb3488d4e4801dc1aa171dad15bb4980e2869379a
- transaction
- 5df5ce636c50e26de572f6f248d19aef803c51cf7783a093354cd4a1c0a373becomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 906
the chainentry 906
- sealed to the entry before
- 544a44f52015a04e11b67a198b8c71bf28aaa9e9a2563866a4ce3c9beb29e2a2
- this leaf
- 904b9ff652436180db7d47f406699c67d994e4aaf116e2ba87d6cbad89c13b07
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BhhNsGE/nM2Hrd8FofkX2upTEuDGSzYZEs/gxRKmr7xePCaoH5PDKnuXPmSNqrUxd9FUx6WwyRderyByD7ykDw==