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
- d6acc298e64f7f03e1d5cfb3e9d5dd8195cf516b3e78cb3cf89c65d54add203e
- request
- a578c8778e8602bc199110bb491dd348e034ec7d326fe8327005538dccf42d23
- transaction
- 3c6d44c09796d9a0e7981183e529b94ebec4604f2bb6d433cfd605f84ed63123computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11710
the chainentry 11710
- sealed to the entry before
- ea316cf88ef47069c1295f45fc42deaedc4d0d4d9968433200d424f9fe5c57b5
- this leaf
- 45e5637c7a8544cce002eb628b03a0becf4295d9278426d3c0da90af40ab2879
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Nfejh+InY3hVJ44vPlc2SHRSjbhHr7NdUwa6EMzC6oCpHkLEZusIk2gNayS62siV5EHwwOwX07Vf+USM9jL2Bw==