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
- eaa9d4efadaf48d047834ea95648eb66617a7cd9a9eb6563eff30830a8ddf783
- request
- 3b9d86a23c835d556b6fcb9630806b47071d922b8fc55e26041ddc822c40f550
- transaction
- 647bd6165f2722ec03e164ae2d828b5b4a30cbdaa0190bbffefc51a3bd3b4015computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44715
the chainentry 44715
- sealed to the entry before
- 867b70afbc47abf52dbc2c1e0b75d72d15672230e7ff1321e156aec3961501f4
- this leaf
- b319299504a0ce8f0390ef70059a929f4b7dfa1cc05f1f31fd68a600e9ffd8ca
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- X3bbM8szpqJjGjNPI3s75mVK+XFo5ehkY/EIk2fT9PoBtdaRKlw/NhDI6PevBJBgE/cUtTkbxhoEec8yK51tBg==