*Payment Optimization Post-Auth Fields (old)
11 min
\<font color="#b6c7cb">\</font> topic type reference purpose define fields required in post authorization updates for payment optimization audience api integrators sending post authorization data applies to payment optimization post authorization update messages does not apply to pre authentication requests or response values below are the required fields and expected values to discuss how to populate these fields accurately, please contact your implementation specialist transactionid \<must match the transaction id sent during pre authentication > soft decline present values 0 1 eci \<font color="#4f6228"> example values \</font> 05 07 3ds flow values challenge frictionless 3ds version \<font color="#4f6228"> example \</font> 2 3 1 3ds challenge request type values 01 02 03 04 06 10 11 3ds transaction status values y n u a i c authorization status values approve decline authorization error \<raw decline reason code returned by the acquirer > exemption requested values tra lvt scp authorization vendor \<name of the acquirer used to process the transaction >