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
- e9216e7a58a235ca07c4ee57cd7e878a07ddc789bc1596a2fc907ec68ebf7a6f
- request
- eb49d5a1b76354a1121920107bac87677352eb58e7169d12bce44a89a7195c57
- transaction
- 81b7ec777912fb32284e88e62e84742388555a3283ef1cc414adcc5ed71c631bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17999
the chainentry 17999
- sealed to the entry before
- b03dbecf1084b70d5d520bdc410bb6d6979b01e8a1d6d7bcd1ab50bea96020e3
- this leaf
- 7978bf40c7060dc78c30e527cdaeb75000c87167b79f79b2b4f267efe01e937d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lCf9R41QRMdxHeb2aW6sYRIx9uxzlmCwJLwOxxJ3GiP9SZKxYl5Rm3cbw8vmEJBwzNlUAmyOoWBdPCp5p4a6Bw==