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
- 1b723d4471a2ba408c4f1f54f305390579d07f365168866e7f88d625708ebfa0
- request
- 864fc97b257c82a33affaa04fe76f67aec80b12e534c12ba081b58b59a312a45
- transaction
- 7673882267d61188cd70ffad3a185ee90bc2389794039db31cd13fda86a5b4bccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51763
the chainentry 51763
- sealed to the entry before
- d1f65be43b44353cb8e2a513855d9ac0cf59aa58c099fdf9c7308af1e9fed773
- this leaf
- 6f4b254fa7764e49f9828cc35231e60fbefc15460c3b60776979ff4b93ecf2c5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rcAAOCT5/jgEqx7DA1zUHk5Hi4ZCSP0lFMYOtewrIK2agd+SaMQeM9tdbEI7RyCGyJND6n4kD62a1TJu6cPxCw==