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
- a08d21bf185f9899f3f5cce7764d4a16a5e9cfd2dd828ab134606a4950cfe49f
- request
- 40e398e90174289fbe55c66446fd086b91ef44e11f1ee93549905e0196b50da1
- transaction
- a045330a42b48d25105486733017b17f790e35f803cb0e6fc6f99806ce2e8bdccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54495
the chainentry 54495
- sealed to the entry before
- f2a5a2a77e7cf1195632f32da15c9ed65c6ff9cf01344e4af9d334dcf1ffa8b0
- this leaf
- 424d4be7edd20e9f663656842be1bc640dc8421ac7a774dc3a1e337bcfe322c4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- V1Ok7fA5G621nv742k/GqrsuX1mq2gsihxaAs2sYDTPeGyKPUy6l+u66pRB/0j179NEyBUazu4/kmxVLOEk8DA==