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
- 86620baf9ac2a3ad6b677633fd084353364ffccc2a70379c1fd400f95ec15f42
- request
- 924f9db85f92c11723d8996a76a653610a6a6ca895a7a0ea96b000e36eb0e2b1
- transaction
- c86c477f6dac1b39692c606df865b8e731e86ccd70b46e064420f273db9b1ef2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45320
the chainentry 45320
- sealed to the entry before
- 5ae28ecf897ade544fe905e3d5b40055929e8286f37f0bc1e3d78f808a344965
- this leaf
- 46437bc0fd12e53f5e089d75e9da3e8a2dc56c5601a2d520111f1ad7236b87c9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cZ7bGeZYkrTM1biWEE6B3S9h/iYfDsodBlUq8g3cULdD6BX6S/zLcF9oyeIYxnT+cOTYT2uCnpNlnLbhAVAvBg==