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
- bc99a913bf39cd31e1236e9effbc11e96bac7ec21d674f989b571765067bf74d
- request
- d11156143ea1f67e698f2769b36d5f33b28775a5b0b491c3d2aaf22f9a295609
- transaction
- 5ca48410666057bbb668e155635b6229eeccae16039190bbf2ce2cf9da5ebe67computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35005
the chainentry 35005
- sealed to the entry before
- bd77150c014e7fb786d284cd327e8c64522c4102d9a34bb8ddfb5f4957455147
- this leaf
- b5644e96c2c20854f8e878c844323b38f88e02d8e082ac60ba9d6021f61c0dfd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- t0utP3R4j0TS+o+BLD+bxoyCl6D0Yb8rBBYcdDONEvrleS6BWsMcViwYlx+/0d6TZr00eMHur2hcT5PjKq4KDQ==