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
- 015f5543441dc60f44d52e353429f25fb6383f6b7a8ab6616e95f40cee205288
- request
- e45c09302ebdab6011cc2ea9be751f14c732faee9ad227adcf2bc2fe05f9a7e2
- transaction
- b5aa905a5b625567a184734f949402d5196f582050a0645c0634ac4dbbee6f56computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21676
the chainentry 21676
- sealed to the entry before
- 1fddda8741e921007d653a7e85b9a917c9708fe6ac5f9f9dbdbecb1281ad711f
- this leaf
- f2b2c1f4c6319faab196fbe12aac1283ce37e102480ff16feab07e4bde654a58
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vYGZWAHddY8HPKf9LuMy418dwDmShq1B/fVLJp53I4ziSptVqZh1OXHHBxGIYeffQZkwGQlGGr/bs+Es4BtfAg==