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
- d9f96889c3744a862830c8ec9a8dfa4ed68b390ee0cccd6be6237a765b50dc99
- request
- bc4a556c952a26cc8189a181be7a7cfd4a18a9ef5ffc71e9175bec3b9b97665d
- transaction
- e74480008de37bb750fd3ef2d3aa221731f969158bb0ada1ca13ad1452080508computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68699
the chainentry 68699
- sealed to the entry before
- 43e631eae630813df26a2cec10043a4fcd2eaea96a304788e06267718b8dbbcb
- this leaf
- 5597e96e44a5ba9fb9d40c5ea40131f08573f6305f66ca7fd2bde8ad47226733
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- r7raBzg2sLQl0Z6cE9GlHe3ba3pupUqMVkw2eBd3Nu1eWLY/jTgDlGafFbz1Dxd88pyfcb/xkjrjxkdZ2lMuDw==