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
- db11da3083773bbe515fb51bc6fa1cdc0e893a0ea1d220abb18e8f87cee7f7ef
- request
- 34685ccbae032a53b343bc1bffbac3d13de63a85a835ea4a94abb016d1a7028e
- transaction
- d20f6c872fa7ca1abd34c210eb9134db8feb4145405397d0ad0d6c18fc6649bdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26502
the chainentry 26502
- sealed to the entry before
- 982a9f967ca04a1d9019fc41b4c7f5d8098a124013c511e98d9f97f48030d111
- this leaf
- 6935836eb76c19b3aecf6696da11aabf2c247e30293a2247df9577d7a0aa4cd7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eTYBAkmB0sdEt6urxDIy889u0k8ymSN3MnbJlNEnS0+khzmLTu62SYL12eClKCXf0fd7UIz9DX3Q2Q1x4RNwBg==