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
- 9ede06dfb1cd2c9310df514b72cf0dc844c11e8f9438d322de0fc8efece80aab
- request
- c1a76306a0f5622f42731dc303294fc842855505938401be869b571aa58b2434
- transaction
- c690ea2b5f5d553dc32a6aec52298c85c2c671002ffb24433ca92421038fe27dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14188
the chainentry 14188
- sealed to the entry before
- 58bfe4a2d5f2a428678721561855e5e08f26ac74b7d4108fd148639ac8eccb64
- this leaf
- b35c2e3b36e0207abd192e39edc4551b44fef6e1fe0aca83eac7e6d8bfc88ca7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oLhKsV6czg69wm9AZGwu2CFhk+bsVYae8hrmfcb8G4VQpHkIEFQ2rp+GjgxCDLa7pgs2jh8N4sOFXw5JV5cKBQ==