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
- ff1198f5457743c244de521a62db9bc30289ab358036a8ad3391afef91cb1bac
- request
- 1516a051711bf9d51bc99a0b5aa93469336dce5125d4b2a1a20354b85ebe32fc
- transaction
- 57b9e18f6006d61fcef4ce9ad873e41704758de8f080d1ad8b4ee3a6a17e7644computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16245
the chainentry 16245
- sealed to the entry before
- 1d3663706db0c647ef3a543dcdd0a8463ad6a472237547f7b509d2069f33794e
- this leaf
- 4511e53190b46842aed24c2721d5e1bc2c722efd12730dfd70d03128c7753565
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EGJU2X59MCwR5drUFScmbjdGyAd4yW0H58cp3X/tbIx4VgysPDLf3aqa8z3i1MneJHgQqZNoKWkJPhPXxX7lCQ==