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
- 419cb51d425546eac419755701aa4057ffd798066ec4a7deb629eb20130521c1
- request
- 2ce47dac8520396d5c90615376a86ea8b871e02c13c95bf7bd0488c080c1cada
- transaction
- 2deaf989381ff7a5b00295d7ba4ab250de258fff9f6071536cc4fa1d443933dccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56088
the chainentry 56088
- sealed to the entry before
- f4cf5e523a703008ce2ec7d20f17aab36d1e12be03e79c1dbf8bb963e85010d3
- this leaf
- 5b38f7223e376f410a661417eb37ab429ef93413f45898071952acb1d68a4a71
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- g5kezLdPEB9aBnQ2WjznL/E8eCfHoDp0VsQsyQhWxvWMkMQTlv8PtzCfuzRdRAVrwYjj5Ea0tmAWpbKqpzQACw==