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
- c1147db1efb538340ba563c26af9bfe9c0fa31919a3b257dba65b01c33fb0348
- request
- 49763d4293732661deec1b1b63113d39b2311c1c04beac6abcca6172296dccc9
- transaction
- cace881b7742c258aa4436608ab5f0062472cf68c918618ca7a5252a900fe906computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20069
the chainentry 20069
- sealed to the entry before
- 9b49500a85ad3687cfba5006c4033129a6a38cf49edcc318ca7943ad4b9c8a1c
- this leaf
- 19538a32fca492460928ae39c7cb0f9cb89fefc1caa5ccd7b175e5376507e58e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /TxOjT0HQUFXoFDDnHX5F7Lk/wuJPk4quJtz9/Bz4t0F42mzfcMRranYlgU5pjRFW/7D6sBnfuNBw4eehHWnDA==