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
- 611796675fe73be427a61b09ea471d12293c927ed560e2e46fff883080ebf5ae
- request
- b48437252686ebe629f8c83595da49c18bdde640111e6d49ff5bd8761e480bb5
- transaction
- 2290f91782390c57a3524c0ca98d0addbf20754e04b97a20f83781c89b6c25f1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32017
the chainentry 32017
- sealed to the entry before
- 9ea169376c3b7ad6a5e96aa6d1df972f8589c8a0dd798b5e8463b06fa840800f
- this leaf
- 842285a37350fec83967d56717f595c3e1e42d6b7601b2cc632fa9749c4c56d1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UMS+zGjZCzibGkYEUXJ9e0H5JxN0mA+keMOIeaQdenpaoax//nrsAN+vCneoQX6jI3rVobJyzYD2XRb2ex9iDw==