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
- 54d5939dc9331d473febf2f6f864e87fb6300b941373ee21f321dcf5ab9a02fa
- request
- 5839bcc9eef547bbe2d85199f18c106647d60431f8c1b0c031647733d55fbcf7
- transaction
- 8cae53d042adae43a52156565ca33c5f2d47d3f2f4896e0dffb27491edc5bdbccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44650
the chainentry 44650
- sealed to the entry before
- c5a24fbca4c9e947dfafb2e854999c07e9006a9145cc322f0b73c8cd02c96e14
- this leaf
- a1980e3953fb0a092ef13261b51ff72c038cd702a6a1b04f8e8f45154bf4b27c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DYMQ8T0rnnVIfmRX+1TD55PNKMKStuF/OrX8EYi1tEjjaVfuTuCHYb3luTMWrFRPprbOzLj9uAgjFKOxGp6MAg==