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
- 3f7047e41fc1bae96f2f9a70a3dfbbb8e4ae7e8a35ec7be9ad68ad917a48dbe6
- request
- e2c0295845cc0b0639f26579c001e9c284ab1455ed3f545b28e05a766cf2640b
- transaction
- 21104eee996c438915c4d30ffb0c830c649b4b5d2a72d67efc5dcb28bcc80bd5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40119
the chainentry 40119
- sealed to the entry before
- 562d0d4b8e069711db7c4117d80f2a08f506338f9cb0d57ba80898feadc55111
- this leaf
- 53f27e6666af36c39b83c5578803ddd160482017bc7de158b274b8c10cd7fe1a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RvN9W/UJoDVoLk3gdHV+W4neAHQ68Bbrxm8lX/9IQcd5XPDiv+8ise0ENS8Mm6mnOMaJ4HUrvnl79TjoKgkeBg==