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
- add5f4f72b154b3ba280a9f374ce45365e6797c02e626ea0597915a9c7edaa1d
- request
- fd30193c72a697752e41c95a5250208a1481e9d3b26fa1d23a47f52bf574dda7
- transaction
- 3769fbfeac4034cd961ca4dd446ff823f65435d0fa6b40c9e395453ae3aacb06computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74159
the chainentry 74159
- sealed to the entry before
- 62edf94bec52e83dde64e6b421d170c6b25c8576c6f687c05cc3b519a9f56cd3
- this leaf
- abe83ba0a328c25c65b7a15f757329e555faa9ab633baae10e7ee3b2e3879cd1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CNuBmoE9p+8ZnBBGDf2ZGof3Zb9x93x/UtvNNquG4Vuc/jtW92nsYRLVbdkEzzP4rYg1z0EFM5rx2qWnE0lNCA==