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
- dc48297d012f044742b9c889d50ab1564d69b0641eed4c246a9d77075c9c4b09
- request
- 01d7825d190e07b7976667003eed0ea723f5bb8010470bf4fb40d120d1d9c542
- transaction
- d07ded69f75ee81d27a2190d7df99ef31dffb16d0877620d1e58b403b8eacd0fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48341
the chainentry 48341
- sealed to the entry before
- b1dc026b98d0106e008adba50fc1557ccd532c215633a3e2d7df9471693c35b0
- this leaf
- 2c0dbf9a2a14de6a5975d4d9d9118d79419812c0e3b85854464839022333d1af
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Liw0e0iy39LtsLa9v6PuwiZ1RXYm/G7QtkayVv9lddBDfIxpRQzpWtGYrO+XKO5YACRGoI99jL73M0RQFczICg==