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
- c069e6b3fff4cd5fa45bb39c8cd66f759fef855bddb7e097504769e274586730
- request
- ba8ebee3a4e9bb27bb950f59ad2904c74f08e79397df0fe0b56d1967e4b9c499
- transaction
- cb51150981360706a0b38420802acebd3b78dad54e3a061c45537ee467927059computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57459
the chainentry 57459
- sealed to the entry before
- 7f7d5a0d5154b8758929238441f79ac7e3f0466e179e528293fb4e97f33e39fa
- this leaf
- b30545d78a4cad29c40b4c6e32e740c2d5b38280a02066db25277687f94f295b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- L8ycoKqwXn6zJ6QUi1xfCBgcji+Mq21Lrqb/D9M/HRIISUy2klxEuwnXJYEJH6ufDh2+CEUBi5DslZQKF8gTDQ==