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
- ca85a049bf0fe36514219c0ada095108b4d8dca6cd0e168b5af8a82138382202
- request
- 083239bcb33df505d3b1c35076d0585e20651a1bed6c075c29f79cd853a82b2b
- transaction
- 04d09d7413bdef58e61aa0ac439383a19d1cb66e7261b2ba32bc132d22bc40b6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10942
the chainentry 10942
- sealed to the entry before
- 894e11c9dfa9de00d5fb12dcdf538ef3f271a661a89e894f6c4d3e7089278de9
- this leaf
- 99139f4f921a7c9c66d95650da896488ae76f4c8062655b5ee0a6b11775ee8f0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KJemB+LE1mHwaWZlmyq2f9jA/7EEvJDmfnxltGlJaMy8pMuT5uhfQ35PSdyCPCoKGWQKPX/xLaxFg2J3Qx29Dg==