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
- 6f8cfb1324a6968da609273caddb0d979c0179cacac8eb6bd5e8a1c03776d236
- request
- 78cfc667dd919cf98890197040a5954d1e3863b4db60247cbbc15393a01d9253
- transaction
- 214391ec739bdb0416800d59d758e4f1b16c54eb0b08cc6d0c117ffff368f53bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77082
the chainentry 77082
- sealed to the entry before
- 321bb9be85a7a620ddc417660b8b7a1f78fb292aad97880236f05782e7805aa0
- this leaf
- f21e20bee660c8cec07e7f86a19d857166c1a726e379e72d9ae0d7c0debba1fb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 102+ouH6RhbEJmG0PVg7Jz5ujlTOK5NUWTRacNWLW5cZ6M/zmJ0kTID6SYQHmLMVUOxeEDCtFlrK++gG28+kBQ==