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
- 0330dc0534fe5cbd918ee9a011e8434db9dbc23531d927d5950f3d086501f70b
- request
- a2ab0fc532750d53a2bbacf79d5dc44b91522c8c4a30b5b831feeef8f5ec1e20
- transaction
- f4bc7609c1b78a0f5cb27de54ef7784d4672fcea2d4f8a0d523faeda4db7b48acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17021
the chainentry 17021
- sealed to the entry before
- 7aecf8717051d380bfa329af44e26cba6e93232bb812b5d275f207057b5cc507
- this leaf
- b5a9fceedd650b5464bc53354dc1bf6109141afb0d1bc36f16c21691c5a26dd3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LXgT4IvIFJwpJyUx47njzqjuzImEyMthnuM+Y0PI8pbxH8IxfLr6FScyiQkU40j2tnv/Va6h1GdmMPoKlUOaBw==