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
- 37effd9250f585028bd2ae8bd4f915e5d10429eb3a31b1c576f1d2b98208ec5a
- request
- 2004e16b6c74b664fd5fce37c91590c4aad8945e81e85d884275b4899dee55e3
- transaction
- a8425ea58803d5e58502c234a517af8391f3bc0a92bd8d3b561beb1301366ac6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62880
the chainentry 62880
- sealed to the entry before
- e108e07fd642684b478c415aea337f8f4cf5c50c8dc7642b468d4aecf3413ec9
- this leaf
- 1fb2be795152c0b8a37e7eee2aaf5972f81fda3c3436c987d8dcd42c8a810253
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Bq/wWM6bmYVQZTr+MyEIiXAdfxlIZxrE/wj1bPkkftsDkdIrrEr032RWVntymCthGMSY87WCvUsOX2Ir4CcoCw==