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
- 5401569082d04cb6e2a5843bda461d9a03aa34e27d2d8658bf00c1c99a9eba07
- request
- 2f0b8f947b29bca23341364433e543c3e16d34391c6418f108e3e3e8757cf17b
- transaction
- 56de5eeb25233e82559392d55827c9766152f8a1f50e4f5d830ef01ca81d405fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23516
the chainentry 23516
- sealed to the entry before
- 8272c355a568a7349a1c13c8dffa990e75c8f054c48cd240af26073b03361dd0
- this leaf
- 235df5812ad5471db9047f7cea367c6642abf92f145570db1f2e8cdd6ef59843
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- uruZlkUgunRIWLtoqSXIM5zLC7uZnXuIWHkieJR7bXn40hamQ8iRXRaEKwZYetgKdK3MRLKIbKz6BVbs+t0FCA==