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
- 8f61527c1bd6764e498fd20bd193a898ac6984bbac2d18e5603434f2662cbdc4
- request
- e3db1df4cac1399b087776a308aea22a9cfbc9c8035361d30569859797f59376
- transaction
- 0f57336d1076d94624d33d3c16f0c5c984ab066c60cbfcda35b274fa4630a0e8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1003
the chainentry 1003
- sealed to the entry before
- 7d738ec4c579e990807fa44f485a2a0908894a486a25af13bcfc1c6e0fc70c04
- this leaf
- cdeb30f36369040884b0ebf2e17f36d7fc2b56ebf7c586cd1bb9198727e3e64a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iTVM9BoEvF9lAVisbaPraASqWeTQ095QE0lh2VeqhbGyEG+mqTCf1+vUDMFfTaXsj0a2cCalBGan+uoBYhzeAA==