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
- 294e18d6c6471fcf6929cc53aa5a5a5ce2e3e7bc6be291085620672504db5161
- request
- b34a0457db62e624f60cf0294a27f38cfbf3595d21efb9b2e506d5e92824c61f
- transaction
- 8ed7b963c517bd5944f2923c846d2e70db7ef3b57ea7ee8dce04eb0e1a58a9d0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61288
the chainentry 61288
- sealed to the entry before
- 2b582058b863a402be5f03aab6789cf6164c2bce527517987aa2620c13598d52
- this leaf
- fb31cd98d181184f35b6370208005f44a3ba63c4db0ecae9c97e9ef9d0e81c7b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Y5KbLeYkKgCKJoZvz8xeSMCHVmRCEY56OJaR0syjoKX7ot7PwiW4W2ezPNxe/XqbBeHiKkmLo7QBU6u33N7KAw==