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
- a0b2881c5f213c142dcb1a9eb5107f7fe040a302f24cb6d2df5d512e090eb9c2
- request
- 487fcf52233a49ee404e0ade2d99af3ebfa383732e2d5e6346436666c7531728
- transaction
- be9b3a11edd55b7a42a4a690ad327e8c3d705ddf69dae9c3ce891f089ac7616dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36767
the chainentry 36767
- sealed to the entry before
- 3d36c65a3b2c8df3b0b254d12c618f431830c3a6e98852dfa775b1a1da1a9410
- this leaf
- b1d4cb72876611239e4560427b6e3050f61dab90c0d209a1f28b4566113ee0e4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VgcIqXCOIHM1mQaHos09IyOVQjeGKYWC9xqOPvoNNTW6LFI1sJWFoK4oJlpEC75Oxsyn3d/SrCeFSShKyfVdAg==