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
- c2e635529f729e866698ec299f287087c89622db83072836ca8973478f72f6c4
- request
- 35759c9b87fb682f2a71e9a4df57d885fd69b7b170e20bcfd4c2150f93fe3c61
- transaction
- 1ab0a2dc6a8c71ec96b02b3a7dcbe10891f1be89902c34cf7de858849175ac7acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23373
the chainentry 23373
- sealed to the entry before
- e91c6126718c9797ccc76a33ebe10e1644e8e71c25eaa3e0f4e7579cb5289ec9
- this leaf
- 4028db2d9d7bd314398ef8e8463b6478d4e19a0b700ff3e6cf41dfb9c75a19ba
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Gj54NT3J1YX2KZNO5PuSRqZInFafLUlZF4hSXuUGCGwBz1PjMpmBV1AJ+igUdRjr42UNmG9/LtfDTAsSe2xnAA==