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
- 9cae96ff45256c8329947e77f3e04b51f835f131e74d9d62474c6e8820cb5177
- request
- 22ba0634f0590e7ffffa8e31e270fb5dd5656d8b10701f9f77041c8e78823095
- transaction
- 890e31444b5e27069c74f5e3a0a38b3c905dbac22d7d0b1fe8815cac2d0935a3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32013
the chainentry 32013
- sealed to the entry before
- 6f4bf27defe84e61a88d02d00138c5faba77d30bff20e469d428db60517ca9be
- this leaf
- 4d06948397ab41c0bf6ecb96d67eed5dd1533aec3b584c332be67f301ba8d0d2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- D3p2ry9HrZETVGjBXOjDRk0sDPvJOZufYlfGYFkPaDrXo7ZqKF4VO4KJck3+ZR7rIms6E6lJf/sGPas8StliBQ==