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
- 5e2101b7849e07f09ffe1e109631eb4896e24feda22c242d1b61219a08a55513
- request
- 9074ae37163ddffbf354c5ad7dd6b1d03e6e80b96cf9a45508a61066adc74ac2
- transaction
- ef117eeeb357634d7020e22ff67b6d4f98bf58701d5877699a2884ed4975fa1dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21101
the chainentry 21101
- sealed to the entry before
- 95dff405d6ee02d85139de78baf435c886ce7c590ea114946d3a18eaeb24d28c
- this leaf
- 835cf5492ea3399cb47274b8b1b3d34d7f9f89f6f8d23bf4e7c0dd9658dbf565
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kslc+coSS5YSbQzLaEbKEP4e07wa4fA61L6N5eyhBStOHRfqlIDYE+xu9aEemAey9byaKR0ITn3Vhn4QPA1uAA==