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
- 00f87ebff87e673655bdf960d91a1deeae99c2607ac1235a2e2324710c1a0b64
- request
- da663104a351e242bbe424c1722e59f127f3f4ac9c4fdb3939d81830079599d3
- transaction
- f9146304500106b00fd58d64462b0bf2c1d62a25ba83def7f506c154ffec6ed9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77612
the chainentry 77612
- sealed to the entry before
- 5b04f08135bbe114736951466fef961c15a5526fc6ab023a1e324b3224cb4184
- this leaf
- 9e1a924b1e3698a067467f659a974ad1074644b4e03cddc593bafdcb7dc15cd5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IHSmEGz/heAiEQ33KhzefecQ/lQvm8KulM3KVOxAOvT6OIotHtgwXL3lrw2NycB4lc4nrql49C2QGGedC+2fDQ==