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
- 6e74ba2253ca7072f702a1112d7651ac930d9fa5f819be15d7058792c6559b00
- request
- 650c5f8dbec8e705913b10b371e74a0ed9cc179f6af69a2abce4cec9b656538a
- transaction
- b4746b896096c6db22085dbd7bba4755d81dab683f913d18d4cb9a4a56c61416computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29983
the chainentry 29983
- sealed to the entry before
- 6a8c5989ea5e066e965342671f337307dcc4ba01d8221c9e0d169411c019f47c
- this leaf
- 1a9785e7727cc42c5818b70bbdbf05f75918fc41501ba3bb7a2d7aed16dcc2e4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mCdDPthp/mm1tulKXig4siLGjF4LIUPTL4NXbO8l8AJ6/6UGJ8G3tXpgsvMYPK1UkRzr2x09RY1hRQMO1dcsCg==