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
- 98e14528aab48255ce5aa715398ffcec1fb359bb5665d1213eb5087cc2fa4d0d
- request
- ae238f17cd022687d15217b467ff6aa0f869eec40b98101a8313605f70506752
- transaction
- 39fe37549816698a646763ade632a525a1de4a691bdba133e120a90150a2ae07computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31046
the chainentry 31046
- sealed to the entry before
- ec9c134c2c852e4f543e6b1fb57fd72f7795e7f1ec17c5a21b39ff3fc14ee41c
- this leaf
- f5d6205ed02f0a1e2ede1caaf53a0ddbd062fe744d92bdb0f3c074e12120b5bc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mBMOTMZsQ9nmTsLwxh1Wz+UvHuT6xrZ6kx8z/Utajxo+Y8eemN1VaeF61/DGN8eOpxLYeZmE9+gdTw6JGEE8AQ==