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
- f761373b2a8c7b34771072315642a976802e78e93c99568e4e73274a89ab8d78
- request
- 2002306a4273724dca9a7a69044cc5470baea1b07bdf982ef0e3c9a0a9639542
- transaction
- 0f49329c53ee238e711c3ed3baad891ffdefee60f1b70ad02f0781a43300b778computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70605
the chainentry 70605
- sealed to the entry before
- b5d1751789df6356f8c386fb006b3ae544f729faf679d9733915fbdc39639e87
- this leaf
- 7d5cc0856a1d20ff5570356718a432c01e810b9e13b0d052067a46c4ff16404f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JClrDKyI0uXKGh/qQVIpbXH861YSF2lcoIZ2N3Ygwx53OHiF+MH8bVQvCkcY4D712X2WsFiK29KaU7tj+/5zBQ==