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
- 29fced9c418fe87ab6c0e9db61e95f58a13ff4eb7515625e02ed7f3dca3d938e
- request
- e0fa2c2bab88e42beba2ef6458a8a5193237fda3c578e9095baa29de0d6fa79b
- transaction
- e84442b63aecafa7f156c68e68eff630005620961ed25f629fc1a98caee0b62fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63300
the chainentry 63300
- sealed to the entry before
- 66abe5a467906a9d9afbf5a4b8fc070f5d6441fb52194dc7f6a0256f9dea3a4c
- this leaf
- bdc54170e4699fe6f0a60f3536a3d3781390adc064c348816cc1cc6f5094d2b7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zaaRVLyA/YsSlH/tXYk/euGvEY1grB86mrSaM9Kq0SYaQFYgxdoAOElG7kFM4TA1t9zVJJ5V5IkRwSARFVlhDA==