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
- 01405d24a2fcaa68ee632fdcee757f42cb7b9181c342dc80b9995ce1d028f75c
- request
- 767a1857ad63bff164f4204158faf79f1db1c106a0afd9a2a1b9c14c58197058
- transaction
- 6f95fc03722566c3fb2deaada0ee294191fd2eda59af76cb68262f76a1aebaeacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61745
the chainentry 61745
- sealed to the entry before
- cd9e39846d87f89a3226ec4ff949f3a55d87d22ddf147f899c549dbf642ee00e
- this leaf
- 1a7991087946243a817597de4de7ec8cc91d07cb33980624b76fade67d39699c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iYbHoFok0dJxuNQuXwv+0IYVhOHb3tVjShzyqKj59mJRDSvZaETrDZ/My7M49h/Qp6Ms++jTMPObDrkyfH6PBg==