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
- 32eab9ca8f3b8cf260bbfafa8e05032916b461bf3048aafda2a30b346e6b9a85
- request
- 70c1e43a6b85956b6ce882cfb329d67ba510dcdbb3f06d7bac6f633ad9363e65
- transaction
- f903fa570387606a9560f3c9ca4aca386102a7f4c8a8256c17d5afa115a3430ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26767
the chainentry 26767
- sealed to the entry before
- 7a73157966e1c2bcaa83867ac2e0c09647a25e22cf25703dcf7f7299f016f8b8
- this leaf
- 507f05f311c6cfda7593369316d82314d4a1369223fdab351fa6be0a53c42828
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4PiIeJJp917hl4IEyVjAVMapopAeySiylhT8Z+o3L17nHECEeyG8B04XjvQem5G/NMCubrVJUDLK09mqfrUoBw==