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
- 5a2bc7622c1b1b86cb63131ca68dbeb665900b81bc7e34e7a33a0c8d531dfc8d
- request
- e08fa4037123fac73ae56564f2dd72741977ff4331baea0d146c7984a7de602a
- transaction
- 192a5a82ab04bf6b982aac3181c99d480fdfc5a134578e03070b77d37da76e18computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38000
the chainentry 38000
- sealed to the entry before
- 022638ca6131b2c60242aa043827f5304083d17b3c8e3ff3bc2be1906553b761
- this leaf
- 9c6885f32583dff13beed7bd6a7b9cfa13895a33af0e0b59e866bd270e4499c2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fSRypWhzMGR+6zpGY0ezqAUP6jCfZkOuzt74dGVTwZVGuUzN2+dZaXvw7Tnew1Cdty+krVRKzzEofOu2aXdRAg==