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
- aa38dcfc3e003147f14730b37f7d2ed97fd3a5fe8685ce9d8feb5e51c45d7116
- request
- 2e5d75d4aa3c9e6302d79268dfe205c3eec7c9d462e528fd116b2cb922fd062d
- transaction
- 8a9832c54da900a08bab8a7d6f96414a9a4212af967d38baeda68d74a3dadf11computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54088
the chainentry 54088
- sealed to the entry before
- 9bd0d5db18aba663ce29b26a6d19bf5adfac74a9cb4366c38755de213c7f8f58
- this leaf
- 94d9340ea23654c708e43b9bd75e52964211f4513fa4b15ccac0b4e0fab3c229
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3277EuARwhJE2VAxuwRX9EapAYtPPnU0JzVFrCScUpG7mYgzQxwBUkTxcsVo343IKmLRm1cAH8+gbrApsUSUCQ==