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
- ec647fa9dbf00001205f990077e30989b755f32de725add02ca7d35eed44db9c
- request
- d34b39308829e1beefc02f107476e466b145a6e47401749a0c8a976e7958f74b
- transaction
- ed2abf6eb936a7b162f6d040bff69baf184e494b9ac862b0815abdfa5704bc69computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51822
the chainentry 51822
- sealed to the entry before
- 2c4b16bb791083def765ca8d901f30188bd20fbffb71a5dc3a8959ff7004c757
- this leaf
- 2d737827942cf240fbe7d380d9363a28bea05210c5d07853cbed4a132e31fc59
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- D1S7GzvYiYXzFIdk5po39U1l/9P8kw0EP3BNn9ME99wNmMOVyjRQY4CSTGULN8g3vHs1illBksR05RkrpJCOCw==