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
- 8243244cec34fdbed1f09515fed4d7237cbced2f5e3248b8a4f461abdb49477e
- request
- 082e3b3fd7b3fd624a4ed9d51fee5ccf7687a30b3895708282ca0a84fc674306
- transaction
- 28b2e2cbe932db65f55e8d4ed06ca65f9a9db15fa1005320d008dfb7b5a4a5f2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36018
the chainentry 36018
- sealed to the entry before
- a727754a512510ecace0c8c3b2059c20a25a6b0619cd3b8a4e62bc915ff7cfdc
- this leaf
- feb4c3f4dc2263020beaa7bc519739e3604516b251c26364fb3ff9cfd7e03368
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JmlBdGY77WnPGzHkNAvYM43miIlMuEVwobABtDPJl+XsZ123H6O3sKDJphAaYR/b6Dxrqzc1XzK2FARdLELICg==