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
- f7e3011725ecea97d3ed72aaaa6f590dbfc911a1a3927ca83ee81691e62538e7
- request
- 5769f1d4a406fcce73a3050de36842b39acb6f7ca6b820644e99837e7ad4e2f9
- transaction
- 022e8680287f799c50bd2a5303668b84e86321207f067077706b986a3c13a135computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27018
the chainentry 27018
- sealed to the entry before
- c9664cc5066659dd965d7420d54c5fcdc5e5a6032efe8d424bc48c86a3f74198
- this leaf
- 42ef8d66904b7f5836db29dff4c88b9058d74f3a5c2c24f842786bfe72446ee7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gG9GF0ZKKv06qE2SRTQJAeKYvaS7UJreIcX6pXRpmKD4MdIucYeWnjvO2QOQcZ8KPTXs5KdT9WzQgHZuiW/jCw==