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
- 26c8aac9efc62ec66310cdfcc8513426e7416c0404b56aed61f6561a0dcf6056
- request
- dd01f3f24900674e73d3b9bcb903f480b9d7ef3f0bd8463c5e06b8a63380fb66
- transaction
- fafd4b49245de6089db77d9edef9261c4cdb92bb9665e6366f5a4e026644fe13computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26943
the chainentry 26943
- sealed to the entry before
- e9b0574ef838d556d8ee2da10604b5b0d075fe84d20c0197d63611c8c0e7bc93
- this leaf
- 829bb28b9b732ee0469e38a69bbc20d206d587453bed937abe6c03f652f8776a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aBQylUK1ZNPYfffiSjVRuqjbetxEAMk1DDCmReIdCXLCfyEQrULlPULkvHwsUYKRR9mbEJl7gKwNBahaLTGHAw==