Q:
We've got a payment that returned AUTHORIZATION_PARTIAL. We are not sure what to do in this case. Should we do another signing with the same signing key or is there some other authorization you need (e.g. SMS)? If we don't provide another signing, is there any chance the transaction might be executed anyway?
A:
Please refer to our documentation explaining your query:
Payment Flow (Corporate Payout API)
API Reference (Corporate Payout API)
Q:
Why would this appear when doing a payout from our corporate account? Can it be triggered by Nordea as a security measure for suspicious transactions or something, or do we actually have some sort of co-signing/limits enabled?
A:
The configuration of a specific user's permissions is not responsible for this situation. Due to the high amount or other risk associated with the payment instruction, this operation requires a separate signature using strong customer authentication and a signing key cannot be used for this action. Please refer to our documentation:
Payment Flow (Corporate Payout API)
Verify a Payment (Corporate Payout API)
Q:
We do sometimes get AUTHORIZATION_PARTIAL as returned payout status meaning we need to sign the payment. We use a signing key - we sign via a phone. Is it possible for you to explain what this status means and what party needs to sign the payment?
A:
Status AUTHORIZATION_PARTIAL means that the payment requires additional confirmation that needs to be done by another person who can authorize the payment. To confirm the payment, please use the endpoint (with provided signing key in the header):
PATCH /corporate/premium/v2/payments/<payment_id>/sign
Refer to our documentation:
Signing a Payment (Corporate Payout API)
Sometimes in the response you can also find a status AUTHORIZATION_PARTIAL with returned payment_status_reason: info.payment.verification_required which means that the payment requires verification that needs to be done via strong customer authentication. To verify the payment, please use following endpoint (with provided authorization details in the request):
POST /corporate/premium/v2/payments/<payment_id>/verify
Refer to our documentation:
Verify a Payment (Corporate Payout API)
Q:
We had a payment, which after receiving the following response: "payment_status":"AUTHORIZATION_PARTIAL","payment_status_reason":"info.payment.verification_required", got rejected with: "payment_status":"PAYMENT_REJECTED","payment_status_reason":"info.payment.requested_execution_date_expired".
What could be the reason?
A:
Make sure the payment was confirmed until the end of the requested execution date. Please refer to:
Payment Flow (Corporate Payout API)
Q:
If we create a payment that must be signed with:
PATCH corporate/premium/v2/payments/<payment_id>/sign
does the payout require additional verification?
A:
If a payment requires verification you will see the payment_status: AUTHORIZATION_PARTIAL and the payment_status_reason: info.payment.verification_required in a payment details endpoint. You should also notice "_links" in the response which navigate to possible actions. In case a payment requires verification, you will find "verify" link. SCA (Strong Customer Verification) via verify endpoint must be done, then payments signing via the sign endpoint to successfully execute the payment.
For payments requiring signing, verification will not be required. Payment verification is a security process that can be triggered by initiating a payment, not by signing.