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
- 49c8a7e9364600951dfe9d9b85daf01c2424ea9d98b226fdf3a48e5ec3cc2d0a
- request
- dc02ec4099da129b03e65e4d2049fa7f35a2371596483418ac2b59538df31a01
- transaction
- 3a7e9b4b733d7471e97d8b2c71585b3b8e52323a539d73c8d1bdd715bb55a949computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2988
the chainentry 2988
- sealed to the entry before
- 1755b34a5ef70128177ff3d84639f2c44bc8c17d4ec634345913f9b8a5dbf7e8
- this leaf
- d027fa8b88f5247fff55694338a617a38986a0451ab355bf8ed7a66e3dfa3980
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- F6hj7pfCDOFXGSs5XuQlp8YwInhISXb2pHAHT0lp4ff4msZ0xUE6MTvwvAp0bvalxZqherIeZo6GZ9gF2n0sDg==