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
- a5c1c3dbe7a4dfc8041db9712642912e3e589ab22b150f1a315b6229ac377a50
- request
- 8b7808be2223b458fac53ab273aa1c58197be1a4276a0d80c1e6220bc6dc9526
- transaction
- ea1e6d0e3a0d4fff1a5023bf2318b845c7a328080922fb3466af47a42ca37834computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22710
the chainentry 22710
- sealed to the entry before
- bf8df5d14c3ef4ce816e0efb92baef4011c5aa8e034a1ccc99070d2480ce43c5
- this leaf
- 2820540373c1729e76dd0284e236c4db23d3c97dc2fd6106d01ca2714dbe8015
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 40epuzRPKNL0q10RumDLHfQ5gk9oJ/GhK6xjuYdHV1z1b5bRBpTDGj4UuldYv7SoWjJdMo75NdoZ3C5YmX3fCg==