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
- e5f667cc0185505f41a0f4d27f0757e0bf43e44d2ee86637e54a79deb363e1a4
- request
- 0c2bc376f96daa9150d3ebac841a75e076f3431d420f77ef2e1f9297a6bc5c34
- transaction
- f2b9b8626380288edfd16ce52ec48b196da5d34a22a9f745eb85cc66813ece4dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72299
the chainentry 72299
- sealed to the entry before
- dddd3a71ee481396b5b2ef70b5f960c50e600ffddeac1335667e8574e633b1b9
- this leaf
- 5f94b6210802b7ee233c86fe86df5d6f1d8eb85ccb50a56ac83e3f149cc82c81
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1i2z3WqI70/ZTcGPvNsOmzAVpM9lLmNou3UATwyE87P4hh01X9xmV2fyzsPmEaqC82Qp2sb+67lgU3AmpAgkDA==