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
- 0241ccae95606f70bd762fd054a059ea583bbf1a147d36cc95086014c72a73fb
- request
- ce6737fc6d06aa9862f317a23e52bb954426185f1cf99c760f33b7bf12a38521
- transaction
- b6297c479c0e2f2903636045322ad22fb17e63ac59233dc1da7a407fc81b8cb9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56694
the chainentry 56694
- sealed to the entry before
- a620c77cdc7a7a7a887c98f237f1f4c95eddd9f9cda66a14ac60e311cb475495
- this leaf
- 2aaad0f7510c24e9c26669afbc06059b62dd2bd60ee562b8f61443d3327c0620
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SiIBi2tc3mg8Tz+bjKuGvaidVMVcyrUOHxH2ESi/AOngLcxU4fmJSSjF/48jbtk0vK09JF6k9CS0rvTIm5V1Ag==