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
- 1a013087bc11a5def4ad21b92d0617b4a12116018b2479c6784d8e0594e75de7
- request
- fc21cba86702b68ed2d898e9eb75b380cf7babfff867441b10ee74e6be64e71e
- transaction
- b2c326d74c8e920e36cd63a8c8652202947c2f89da0fa20b4d4e8dfe62730b89computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67058
the chainentry 67058
- sealed to the entry before
- b70004ceb0d057c9c82c6b3626be1f934baefde1de3b959f62e504724578971d
- this leaf
- 8b6c0c34e9287392fe2eb06f2f5f871036c0e4111e187b430fdebc2ae9caa4af
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IQrTS696aLUI1KlV8KowbWDzrZZhGmrTiPrCCFCMBb4B2pnMCdFfsRMX91KZFu8YG1bZggKiAv+8EtJo8H2zDg==