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
- e33906935a9b695ee699424ed359aabf98ce2af364c168cf3d80d9fedc0c7947
- request
- d288bd8622af0807326a8fb9fcbddd8b027f2bc78a2970c96ee264912a5eb93c
- transaction
- 4e40e064b9c272e95c6d6179ec2d998d43cb6074472d37d9228f4fd3eda2d9eacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43392
the chainentry 43392
- sealed to the entry before
- fbe21235b8764c861aaf48833cd620f96de8d43b4a4f487bb1bc9ee910e005da
- this leaf
- 10e55f03b9d4aa49db411569a03e55408d847aac4774682cc926767adbdc0fca
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Fwa8iKhTaUJNLMvOZqZo4G5vIjN7nkuM/3KSbftQrKBbnkSPJXI8tSaeWHQYAC8qCWmG7TD2p77KpwZycbdvAA==