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
- b40e484e62d9d4c47e5aaea4c9c94d7f1d8facdf0cf2e2dbb6287b5e77b38e41
- request
- 69d4472282d4342eea8ca5681484ba640037b1e59bcef4864ddc7f0ca0dc5ab5
- transaction
- 2ce375f41791a27f584bd30daf707b3c944b1c8a112c5754fd0e76e2ce00ac0bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38843
the chainentry 38843
- sealed to the entry before
- e2c9d3bc0f4c3c7df131c9ae54db1b006a4115d1e69f2b95fb07813da4459916
- this leaf
- 709b59f834655098c7603985715a36de0cd8c676c75a5b66d97aa596954ecf85
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qu/eW/cVr9L93pFcypbowzuoqe3vcs0ONWhwAakLfqt58Q0ty9jvpawqvLTlSNuWaKeYrlmPx7LPm9dZ0lTTBQ==