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
- 5dc7b01bf179b4d0b2d7bd80b910149a6bd34ceac0f7a9e8bc41bcda92b682fc
- request
- e948f0d7d8b55d422ce7f9e57a1522483d889d77247f14bdc8e9dddc106b1fc7
- transaction
- 91a11d605d0b6883d233b55bd62a21d47c615e88766a297f17e9cac3a8db2b1ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2310
the chainentry 2310
- sealed to the entry before
- 496ebbf4ba97ef749b20417c7072c5f656efa47914f983e7f8f2f49ffcc29c8f
- this leaf
- 0e7f0e2200752dc27d00fd92e7f17c162a7337a9cf5136e746d54911f919f1a8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- X5Zl+9k09Vn61a0C1o8JpNAQcKA9VLV+DHWqDUDKfbz3J4mQgqViMiPl1ZxvYPmClb010K3V0zC2owUIXTtLCQ==