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
- d7b45d63b4df97d6b8496f0245ddf0e1512bf138215517f79b1816aa0db70784
- request
- 5acd164fbf27db45a5624b908b94156ac7e48b215663e27c7460f3dce1f68264
- transaction
- 91b3dfcfe7095738497f29905d4836cf8a87ce4b555cea3510ca51762392344bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46396
the chainentry 46396
- sealed to the entry before
- b82d95e3c274e7ba86c48601b3a8d6cbe01eba11a48148c8a83984ff0e53106f
- this leaf
- c58c629e8cb0d39a1e3d40642b5315c84190068612a48a9bc2a32092bf456cfd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Q4dDQd+86iLCGA6MLHi2ExqOwxyBx/JOkyHdCQCB48mBlNIimw0CXnRBEA4O4cJM9/3LVNeSsNdGyeS99QwTAw==