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
- 70e82d934856b7e8a0ef10dafe983b3c9c151f17a3627158b4fb3cb38e20ce3c
- request
- e24672376aab9be1029091040e1994bd0e22495f51b3b6c343b262517a545980
- transaction
- 557dfff4a6ff3b8b155d767f78b452ecffbf358a115c9601ef5bbaa798a21b3fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51066
the chainentry 51066
- sealed to the entry before
- 3fd2829a93d48ab0871523019b8025e10a05eb376462fa222dd32cb500353a34
- this leaf
- 3973f5fb45309d1073a86112966545e8a43e843e63ff5ec0f2bd90548364570e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- G1NY656Ooxz3aynnHk33OUe0phz0XDOi4INIMBc7uyj7cTUJrzXVg1QFN0rbDGhCP1br6IZVs95A2IaHPyorDg==