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
- 0edf0aa0efecfa8c1c155c20828718dee08282aa4ddc8245527aa3924502089a
- request
- 8814ac86cab657adfcc0bb7f3ad90c35e76853fa1ce70a84ef03adcc85e8cc56
- transaction
- 1aaa503b34f53469bd88fa82bd5481ef1f4e287e49e62c43f83bf4a8997770ffcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44363
the chainentry 44363
- sealed to the entry before
- ce6af45a1bc58d1ffc5f4f3c921871ed65effd40741f9656876d8bc97a50a844
- this leaf
- bc6e082d0bc75bd3013624c1e844e50bca50c3e5d1a4b33b9e29787bfba36c7f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HunfQX+GRH7ea5vXGD1k8FVhQ9s7ZkKLhYV+6d9zPAokeZMjHVslrxAVGRb38krHlfOj1zVfLmC24NQ95IHyAQ==