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
- 1afa36464a9817c78d9ba802523532668c7b0b1815e436debde99a0385324838
- request
- 1ebcb4923a95535a2147949074928624f5b99ae259cfd556103e7ef5e68a700e
- transaction
- bea9a26a325e0bdc3b8e17b9848c84dc9812f387ae4523e7b0d0959d67864e1dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30073
the chainentry 30073
- sealed to the entry before
- 4401df6cdd9b3f036ee101fef92b8109fd3be6bf220ffc1af5f710d47a457e97
- this leaf
- f4511930164334008f1c5f4407d20df2023a820124a57618a921be05a74bb91b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FW2hLQKq2zkunD1hpIl87/wykqLp7q1yy0bXFz/oj7R4jXCW6YtuX5EfK91zLZHGG6AGvEssddGpEPK5JFTHAA==