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
- 883a101094828ae473a31831ea91d4eff1bb82b461608d00fedda0a8094b0b2b
- request
- 6b36be4f112e6a80262b0bfe0dc23cd1b230235f5d84f7051882fd3ad0ca6fcb
- transaction
- 29009568fdcad946c41866033c848bc98031ff3a496fcbb8803559e3ed895186computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13573
the chainentry 13573
- sealed to the entry before
- 491dbee0c29111562ec43656f952be80169328a8751e4f88ee9f2d2504c5a005
- this leaf
- ee0dff843bb32ad97e18f18093f9e84da41a2a3fadf771f59eff68354b9812f9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GfIrWO0+H1IEflhuj6y9lDlk8gD/clwEefQjK6nJaDiipKcSAvK4ChvrbRfprRfYZWTqneOHMf/LtalTEHboAQ==