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
- 39b44d2faf091c666110b6bb9278924b631aa4720d2e4d3b534ead39d9a7420b
- request
- a4380cd0d90f29268d101eeefce204b16f8dcecfd39a3ae7f49cd59a2cf5485f
- transaction
- 62a84db00d0978d56fea7f7e8443685860d0ac1c73d40cedf652495c656ab445computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39507
the chainentry 39507
- sealed to the entry before
- dc7230a5677845e6bb5408d540d37163edd38b5d41946a852659a898e09e9126
- this leaf
- b8caffd633d0a4c740b2ccc27b7e4c84e6460ef638a7435b14c05240be4e0805
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fkV0+ceyqLixqIanWeBRqoHNa5n3xUJYnSHGANPyqYS9vfWnlS/PEjP8rbduEYGV3K4J/5nuux/wwSjRJorsCw==