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
- 5ae8ceb469aaf5e62d6c7906c9768b5bbddd407d39fbed4f4803a989524f0d0b
- request
- 396f6087dbfd6150bd3aa8461c33407f44d0350f41e9fbb11866bf35b5be301c
- transaction
- 678ab195627dd5efdbee75114b00fad8405cef1baf50d8882eee25eead166747computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48535
the chainentry 48535
- sealed to the entry before
- bf60e28545b62e4044576183e14836279e473853e6d5c4668600c10fe6ea1b29
- this leaf
- b91dbb32b23333e2086196cce5a3f3f782d1dca2b2e7b4370fe2cb54b0c38d35
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- H15jTcKEw0/GMUX4tR+thL0GspnSzh3bwWakrMKX60K2ST3uCXXijixWVupC4e5M75+Yjf+nVbmp8Mqj0HaBBw==