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
- 508152ce542f8775498ba0f0d44ab85cf5f958d1fbab0b0c56ca3eaed13973ff
- request
- 2ae83c8ee8b665cea2dc0b1e607125f2cb50b45942e1ba90f7ae855588498138
- transaction
- 2e577f3638f78db568f9310de343d87a37c9c719a6f99f3ef76396f709f523becomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50873
the chainentry 50873
- sealed to the entry before
- 132f3444a97dfe923a8e408470b7747288135122068cb49a8a5f790d86075a8e
- this leaf
- 0d55271137fc610954323c7101c1069cb83e599ed05afabba4061112a0ca59cd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jBKDQos/IYb23fwjr9uJ+HJ9lfKiIQV6yi3mTEgj1y1OE/EZJ/IwoJ9nnc4NYYBI5n1MgGh5Fyz/Iv6cPlHACw==