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
- 758d2d690b1b12f318aad5570cae5b59b7a345487400053391dad0469649670f
- request
- 0f5e9bab4ecdf63318ffb53ce106d8e2adb440c11c34b0bdc8d09fdaf86d6910
- transaction
- 3db6ae54598f9e33213d27c1d6f7b5c5c17a45679576642512f6def488046a26computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50836
the chainentry 50836
- sealed to the entry before
- dabf9131f3047bec6dbba40ce7f604a52ef4602768058b5df57382fe1bd41877
- this leaf
- 0a43027bd8864c5d9d2bebe684cd3b00ecc73a87ae8b0877f3d7ff3f3515824a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- edkGUr+67983PCXmXTJUSQio+A0e6xCHuuLCNuDNCP8Fz1qzbwPQGCVVJqf05NgAHkH7abGS3e63oVsOFc1nBw==