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
- b0bc1e9bdbe98bb547f0b0e3299b6d3e81fa85cead40ef881a70de3d16321fab
- request
- 4b4c1e697289a9a30d42775a4e8bc573ca1cf1185a1e45f0ac59d7f875ed8b6b
- transaction
- e675f822344ec7ee4d7cd4418f0726d880f55a15e82b244705ccef8eac04c4bbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34872
the chainentry 34872
- sealed to the entry before
- 9539bd76ea72f66b99f4a97e860d79f6b22f40d457574fe35aece9965deeb47f
- this leaf
- 3919fc92f5b5a71fdfd034fe4442b79b05370b45857bcbced5345ffc3d6eed99
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- r+RLPDwGpLzspLiZRDKSP2ZsbbIC5mNfscMC6VTpMbEP0WkKSKdVkfmtKBU9E8VEfroTacnsDj0i4SJSOMMpBA==