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
- b8e09e92885410e8386fc7c0cc66e4956dfa3c08070d02c769b096b32c39458c
- request
- 809753eef26dac6a3dd459150ea9dc5c834790f5f00a3f6ed9fe23226868f23e
- transaction
- 0990b0515935da0e70f899b7f954bd58b37d97c54f9217dca744cd35e8731078computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7452
the chainentry 7452
- sealed to the entry before
- 0ce64b9fa2cd840f299d76f66faa6a6e86436f3e99eda7b325569cb7bb3fb2bd
- this leaf
- 5463f8d629ab283f8af41711b5ba36662e3ce3b55fe7a6adb37f7d8b414519aa
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0e7aUjtkiBVyr4EGzIVBHvgpbBKpi/F2/sS8KCDrMSKUUzOIQWB+uDOuxdRnemSQOh1vAQp1xQFRnE9my/mEDg==