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
- 9c45dd37e1be3793ccdac0dba42735d3c9b42cd7cea305f54d4132115e0389b4
- request
- ac80a431a3e65b3f4f285741efedb9c3c67c714566ae2893029a8a4ea35c335b
- transaction
- c77261853be486b228219155bd7a2e59a1be9efef95ed4fe4df885cc280c402dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 19095
the chainentry 19095
- sealed to the entry before
- 96fc86974a9be01ea77ec9c95fc2c4fcbec41e8c977cb49d4a8d5b505ca84739
- this leaf
- b37190e0bc657d8bf313334d892abfe10bdf9b18e44a0954db9cdf4449c1e834
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JYIYZWvOh3pPIQY02oCX4FTKUfoVyNG1FS0rkxNS+YgquhCmKvKynjynO04bbQw3ouxbm65YvVVmoW2ZiPXADA==