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
- 73faa106df1fd29ef57d628c2b85f27fc9ab99e0002daaf3376765da4c447617
- request
- 3f8730e18e1b3a717ed2aaeb2fb8e51e13b4646ae3bafdb85da6fae6a4721cda
- transaction
- 41fa094d782c6b2cac7b4ed422c76f208b03b82b1fca48ce51ec4e2ebd26c4a9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73430
the chainentry 73430
- sealed to the entry before
- 07cc63a1123a39ed9fefb1992d282392016d03e4ec8ac2a7b4baf548ef023b30
- this leaf
- 7b29484a6158715da2f139d07b8e54af5d73361eb0d8f3f11077e27e9957bc33
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 07KY0a1Ja6fxshEkm+/diklJB92egOGDlXKeibj0LUUWE+bKp1n90zaUEpotxKzfTYXbr+it3jroK3tkjSMtDQ==