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
- 2d4840b86e60d98a5f3d7065d8ca024b2a09ae900b3efbc7d31560cd7efd0f6c
- request
- f2a9dae4f09431795f08f5a5d76e886aed5e9a2794798ff42fc53733e487f46e
- transaction
- e9deae72366f1535fe0cedf9306d4d84a8a1300403cc8ae1358d357ee675f366computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 306
the chainentry 306
- sealed to the entry before
- 66a833fdd4f27fca756f28e5a22afbe8b1b77e74700ea824d03aef2ea34c10e1
- this leaf
- 6e6df96e14f9774c5b0b185a92bda2197b1195983293d7146959fc24c706eadf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7aGfKm++DMVj7+EPvpj7ykD01M8CFVx3LHYI9WEpCvR6BbwouOcKc/vqt1Aincq+gTgLW0b+OJC/SF1QDUg2AA==