Receive association result notificationSignature required
After trade orders are submitted, Worldfirst will call this API to notify the B2B Partners of the trade order submission result.
Structure
A message consists of a header and body. The following sections are focused on the body structure. For the header structure, see:
Request parameters
notifyRequestId String REQUIRED
The notification number of trade submission results defined by WorldFirst
More information about this field
- This field is an API idempotency field.
- Maximum length: 64 characters
extRequestId String REQUIRED
The request number of trade submission results assigned by the Partner
More information about this field:
- This field is identical to the requestId defined by submitTradeOrder API.
- Maximum length: 64 characters
associationResult Result object REQUIRED
The trade submission result
notificationType String
The dimension of risk audit results or order association results.
Valid values are:
ASSOCIATION_RESULT: indicates whether the association of trade orders to the fund order is successful.ASSOCIATION_DETAIL_RESULT: indicates whether the risk control review of the trade order has passed.
referenceOrderNo String CONDITIONAL
Indicates the trade order number provided by the partner.
This parameter is required when notificationType is
ASSOCIATION_DETAIL_RESULT.
More information about this field
- Maximum length: 64 characters
Response parameters
result Result object REQUIRED
Result of API calling
Request
Response
Request processing
In the request message:
- associationResult.resultCode: indicates the trade submission result, see AssociationResult section in result code for details.
Note: After the Partner calls submitTradeOrder API, WorldFirst create, associate, and verify trade orders, which are asynchronous operations. In the process, it can not be retrieved by retrying, in the case that the operation fails due to the change of trade or collection order, for example, a collection order is refunded.
The Partner needs to update the order, change the reqeustId, and retry calling submitTradeOrder API to submit the order.
To verify if the message is received, the Partner is required to send the notification to WorldFirst after receiving the requests from it.
Before sending the response message, the request's signature should be valid.
Response header:
Parameter | Required | Example |
Signature | Yes | Signature: algorithm=RSA256, keyVersion=2, signature=**** |
Content-Type | Yes | Content-Type: application/JSON; charset=UTF-8 |
Client-Id | Yes | Client-Id: **** |
Response-Time | Yes | Response-Time: 2019-04-04T12:08:56+08:00 |
Sample of the response body
WorldFirst resends request notification, if the Partner does not send response message to it. The rule for resending is:
- Maximum times of retrying: 7
- Interval between two requests: 2 minutes, 10 minutes, 10 minutes, 1 hour, 2 hours, 6 hours, 15 hours.
AssociationResult.resultCode
| Code | Value | Message | Further action |
|---|---|---|---|
| ASSOCIATION_FAILED | F | Invalid parameter exists (wrong data type, wrong data length, or unspecified parameter). | Update the trade order or its associated information, change order reqeustId, and retry. |
| ASSOCIATION_FAILED | F | Invalid amount parameter exists. | Update the trade order or its associated information, change order reqeustId, and retry. |
| ASSOCIATION_FAILED | F | tradeType values are inconsistent for trade orders. | Update the trade order or its associated information, change order reqeustId, and retry. |
| ASSOCIATION_FAILED | F | Abnormal collection order. | The refunded collection order can not be synchronized in batch or associated. Verify the collection order is in success status. |
| ASSOCIATION_FAILED | F | Access denied. | The order can not be synchronized in batch or associated. Contact WorldFirst technical support for a specific reason. |
| ASSOCIATION_FAILED | F | tradeType of a trade order is not supported. | This type of order can not be submitted or associated. Contact WorldFirst technical support for a specific reason. |
| ASSOCIATION_FAILED | F | Abnormal trade order exists. | The order is abnormal. Contact WorldFirst technical support for a specific reason. |
| ASSOCIATION_FAILED | F | The number of associated trade orders exceeds the limit. | Update the number of order associations, change order reqeustId, and retry. |
| ASSOCIATION_FAILED | F | The intended association amount is incorrect. | Update the associated order amount, change order reqeustId, and retry. Note: The submitted order amount can not be modified. |
| ASSOCIATION_FAILED | F | tradeType values are inconsistent for partial associations of the same collection order. | Update order type, change order reqeustId, and retry. |
| ASSOCIATION_FAILED | F | An internal system error has occurred. Do not retry. | Contact WorldFirst technical support. |
| ORDER_SUBMISSION_FAILED | F | Invalid parameter exists (wrong data type, wrong data length, or unspecified parameter). | Update the order or its associated information, change order reqeustId, and retry. |
| ORDER_SUBMISSION_FAILED | F | Invalid amount parameter exists. | Update the order or its associated information, change order reqeustId, and retry. |
| ORDER_SUBMISSION_FAILED | F | tradeType values are inconsistent for trade orders. | Update the order or its associated information, change order reqeustId, and retry. |
| ORDER_SUBMISSION_FAILED | F | Abnormal collection order. | The refunded collection order can not be synchronized in batch or associated. Verify if it is in the status of success. |
| ORDER_SUBMISSION_FAILED | F | Access denied. | The order can not be associated in batch or associated. Contact WorldFirst technical support for a specific reason. |
| ORDER_SUBMISSION_FAILED | F | tradeType of a trade order is not supported. | This type of order can not be submitted or associated. Contact WorldFirst technical support for a specific reason. |
| ORDER_SUBMISSION_FAILED | F | Abnormal trade order exists. | The order is abnormal. Contact WorldFirst technical support for a specific reason. |
| ORDER_SUBMISSION_FAILED | F | The number of associated trade orders exceeds the limit. | Update the number of order associations, change order reqeustId, and retry. |
| ORDER_SUBMISSION_FAILED | F | The intended association amount is incorrect. | Update the associated order amount, change order reqeustId, and retry. Note: The submitted order amount can not be modified. |
| ORDER_SUBMISSION_FAILED | F | tradeType values are inconsistent for partial associations of the same collection order. | Update order type, change order reqeustId, and retry. |
| ORDER_SUBMISSION_FAILED | F | An internal system error has occurred. Do not retry. | Contact WorldFirst technical support. |
| VERIFICATION_DENIED | F | The verification has been denied. | The order synchronization fails. The order update is denied. Contact WorldFirst technical support. |
| ADDITIONAL_FILE_NEEDED | F | An additional file is needed for the verification. | An additional file is in need of order association. Log in WorldFirst and provide supplemental materials manually. |
| VERIFICATION_PASSED | S | The verification has passed. |
Result.resultCode
| Code | Value | Message |
|---|---|---|
| SUCCESS | S | Success |
| PROCESS_FAIL | F | A general business failure occurred. Do not retry. |
| PARAM_ILLEGAL | F | Illegal parameters exist. For example, a non-numeric input, or an invalid date. |
| INVALID_API | F | The called API is invalid or not active. |
| INVALID_CLIENT | F | The client is invalid. |
| INVALID_SIGNATURE | F | The signature is invalid. |
| METHOD_NOT_SUPPORTED | F | The server does not implement the requested HTTP method. |
| UNKNOWN_EXCEPTION | U | The API call fails, which is caused by unknown reasons. |