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
- bd6d6460a7b372da3f84e96027638ba4ebc5012700b47fb7afd226f90ef2b551
- request
- e8a9883b4ae243e7ebef72ebca2986bb93334ccae2980570dc1194b80e9fb60f
- transaction
- 26b7a6c6ab2f24c0d5c1bccb90c35f74e45292f584976bfb05591e1cb46d4e70computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6800
the chainentry 6800
- sealed to the entry before
- 41825ac214984df4b8ac7c593cfd7944222e80d52b9da6cd7e7368bd9545e1a4
- this leaf
- e789abd72a4f29176a823a40b25cbada2d96cf63fd4dbe20c71f2e0f96a0ee4a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +Zbbn2fDFMsbroORUfRKXKiqTfS2rZpsbJsxbNhu22yXrIJWOqhpmX5hBA2RyfBX9p8Ki2k+9lcraCjnP9KpAg==