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
- c0aa2aae5d8351f6bee701aefe13485915eeb0b9ed99fe3d9c003cdff8f4f8b0
- request
- a0da204534f660efce66993864545dada6ff32bd1dfc0078ac91b30a0ed28d67
- transaction
- dab6879abd298b07213470d38979d471e2cbf10a4cf7bee822bbc615dd811c4dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76744
the chainentry 76744
- sealed to the entry before
- 0d2f96aa86f80660fef233deb5764a690fe949e941339ded3c5a251b7f72301c
- this leaf
- 593389d22797d5f2e650c069f825b4b5243ba6a0f96ab9083b8b3fe095b8990a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dT4xtfIz3KceItMUXLt9XkqnCZxso7iBsPKWBi9JJu7fZBHO3QDoi3IDlxzsSqyIuQRBOYZy5FUbIObB8DgmBQ==