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
- c627f2dd23cb04920b8cd5ad1ffe16d0f8346af9d6e7950e3b7ef1296bd49676
- request
- cc16b162b8bbeac3445628b0500c224f1f6fedcc541551422e9626d18232d169
- transaction
- d0d27e19acf31b65f87ed19ceb5d1a0b76001a1c11692fb2c40c538d87fd86d8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63003
the chainentry 63003
- sealed to the entry before
- 70c3aff8912ff83de8a0b1bc71d89715e8395224fe8966ec9ae58b3a68228c2a
- this leaf
- 07f5ebacda2d264de117d7be1b97f34463c132a1f016a10f939143966b232fcd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PYBJ+Mx9Tbxa6PMrkkcjUZT73rBW9TNpVPEw+aNEiZhijqClbbs2K+V4iSIWXdq1ocWKCX5or4tFphTDK/QEBA==