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
- a1527d7c3ffb37438dc0299c0327efc06de7e02d1cfb539c47d546397339e5d5
- request
- 584dd8a9cb74be8f61954ce1a94dc7af398b10fc7ed4654082c5c55430d93cbb
- transaction
- a4d9c454e9cf99a44127b64f3df8b6f9be7e495a94cb304a83bd65fdb7fce9f5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63285
the chainentry 63285
- sealed to the entry before
- 648b1281f6f64a36713517316246227d3597842df645c4cc44866fa2a75cd4d6
- this leaf
- 9a2aae980c4106fe781f30c902aeceb8403a67d2476a53cf56ad7aa0a7fdac51
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9m1yyyrnR6WQIkvr9soyzNPdYaFM6a0Q4MaTs3S1HNwMbiMHo0e6x8afGEpjoX/W+MfJH8HoD76QU9p+hEDLCQ==