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
- b7c8520d816b7edd10034bed482607c1927c59ac50e7fe15ef8959066896b27c
- request
- b43dfcbf7be2a3df8e73962e72e4bb7854de4bf385dc4563078e5d7178b754e9
- transaction
- 64a32a27628084aed428bab4737235f851e8b2c226707c8df7a5d4ee52f9b2afcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15021
the chainentry 15021
- sealed to the entry before
- 08c5b51c0ece5ac539cc0e59f29f5b8fc65c0c2a8f63a06f19102f81b2973837
- this leaf
- 5ccee09ac8673a6f57ff2e71fd0996301e9bb14d742fef11b474cd13d60522b0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Jv7M35AAssKnudKr/GQXe5QlTtUES8+C5E1J/lj/ZqUXCor9MOH6KqsCc8VQBu9hRNk1Eb/hGcQ37kS6xxs3Dw==