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
- 93d7db236c7c8d5ef6b9e0a4f722a603ec94a76fb9ad9cd13061c7a5e288b0db
- request
- e7a626bd2e11f7186d6bc8e5f4c9d3144ad6f74c7c8bbfa779ba7bbe6ceeaf13
- transaction
- d18c5104d1567c698d29cbcaa788bc16d104193e34299873a115691a472a960ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9638
the chainentry 9638
- sealed to the entry before
- 798ca6a45b3d47893568ace56645174efc83fc36bfd9c330d196f4a4de8d8b2b
- this leaf
- a0c6698bc577fa5b2d85b59fbee5980933eab76f21e9386f25a31bff825befa2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- G+/YwsjjPOcqDecnlruIOhwyHiaDJr5Z+KeyR75Fu6yZZlrC0fYgS1b1WcSUtEeDUjECgMRUgNfOE/bqwit7BA==