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
- 5c369919ec3a3ffe6873bf83faab67e518b932418a98cef2a121c21123bb9259
- request
- d3822ef32d2557f0018324dc3e70d41e02a4706101624df17f5911c4c60325c8
- transaction
- a877e8a7464eed39ecadae87f0f51670ce5e6c2169ba3d89bb1d85592201366dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35886
the chainentry 35886
- sealed to the entry before
- bd8d7215291c6e064e8fc58bfbf4aead61fde0fd1b806179dd854a3ba6781994
- this leaf
- cc487f232dc6a8d6531b5d2bb732a0bbfd35b03c17a23766fda20cd30251d734
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZW6BMebrRSqEdHpfbjzkL27+HhnFPoiGJmUzMv8FfxNRo8SgN8dft/1dz8L/IKVc7E/4UOmZjsZXDiH1WrBWBQ==