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
- 616f0ff365db67124242668a6dcc6728b6d9ec0703589b82e6c8214aaa7fd398
- request
- 3e5aa3c6f503040114a1c3b7031fa60dc6a5486159a750f5bb614f5fc882b9b2
- transaction
- d8ba30d2460554fa09f2d6a997e4e35fdee31853fc5c3cd140e2bc7d4e01e6facomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33186
the chainentry 33186
- sealed to the entry before
- 8dced62ab781c7805c1b690b9c69fe6c021c53ee37d88cd552d486bbe0cc28b2
- this leaf
- fbef4d6088a8f030ef2cd11e9980c43321eedb8eca5d5d65bffff1160ee5bbef
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zHozg029v9sfGGJE5uLsQpsY35QQmjSElU+r8ogzctVrbSsT8qvPaymUX8KpvMW1edp/Q+C00HtBqxH6sC1jBw==