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
- f5ab540802afec73f74c7e3ae0ec8dc0bb458baf832f7ae34edf46242fa0ec5f
- request
- c14f93a96b2dd012cfa1d53e517ec1bda4a472cdde39b96544145a802dc21139
- transaction
- b6fdf6e6da551e9589386570969bbb6f885f5c030aa716f2116cf2b207b71c54computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51857
the chainentry 51857
- sealed to the entry before
- 6faac63ed9641b3c6a566b351dde7ea2ee1ed37c7e9375368c400aa9120f9162
- this leaf
- 80dc0fb495e90fe893eeb465b2cde238981eb95604002c06496d9ca02c744819
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- A7fZHhghRgZqWB+twFHIEdGXnDMscfyGTXPItGAbD8EAtANt0TtfqYd7siAlQzZD0KFs3uXS5gofooaw3xA/CA==