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
- a975806f160182aaa0d19a173b08cc38368dbb0d49037c169f39e20c5a5ddf3c
- request
- c1585b8a43757a5a4fdaf468ff457734ca16c9aab8ddedf09f8e6f736fe85f35
- transaction
- 5aea71f8e1bb6937ecc91afaa0c9cde93f825b788333c874161f209b34368645computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53858
the chainentry 53858
- sealed to the entry before
- 647e33038f11ada6434ec66479a1fb42ffbfa713c60e5bf795ab9462cae25c1a
- this leaf
- f6536f5b8083fc553dbb0880c4c5f47cffa5ce2cf57d8acd32d14de291ac5f07
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NULxoylk17rhM24Rtt/yLSdFxWeug1V/98R28gNudcGDAXRlX8VLd5FuutbR9DJeG8poDpQMYchdQQeu9BLdDg==