Q&A for order
Identify payer and receiver
The payer and receiver objects are defined in Register order and Register order - client mode APIs. The payer object is defined in the main structure and the receiver object is defined under orderLines object in both API endpoints.
The payer object is always required. The receiver object is only required when the payer and receiver are not the same person, for example a father pays the bill and the son receives the order. The payer and receiver object contain the same fields.
No. The system will automatically recognize that the payer is the receiver if the receiver object is not defined.
Recurring payment and prepaid order
Recurring payment means the customer has given us the permission to deduct payments for services each subscription period (e.g. each month) from the customer bank account or automatically charge the payment card at renewal. If recuring payment is enabled, then
recurring is true.An order is prepaid if the customer has already paid for the order. If an order is prepaid, then
prepaid is true. The default value for prepaid is false.Support for payment methods
You need to contact Unite by sending an email message to the Support department. If you are not sure who your contact person at Support is, please send an email to support@mediaconnect.no.
Some of the payment methods support recurring payment and prepayment. This information are described in the description for the Register order / Register order - client mode API in our API documentation.
If you want, you may implement your own integration with different payment providers so you may send order as prepaid. Also, you may use UnitePay to process the payment before the user registration and order registration. Such an order needs to be send as prepaid as well.
Choose productSpecType
All single products, which is not a subscription product, issue or article should use
productSpecType product.All subscription products should use
productSpecType coupon.You should use
productSpecType issue. In order to understand which fields are required, we need to know that a periodical magazine is a subscription product and a subscription product (productSpecType coupon) has a coupon number. The coupon number should be defined in productSpecCodeand productSpecNo fields. In order to identify the single copy of the subscription product, you need to set the issue code in productfield.Easiest integration
How to register order
You have a to fulfill the order by using fulfillment API or fulfillment URL.
You should use fulfillment URL if the order is not prepaid and fulfillment API if the order is prepaid.
Yes, if the user was logged into the system before order registration. If the user is not logged to the system, then you use Assign user - client mode to connect the order with a user account.
Assign user API
This API is needed for digital subscriptions only. The order will be associated with the user account, and temporary access may be given immediately if it was registered in the order.
Temporary access
Temporary access provides users who buys digital subscription access to the paid content until the order is completely processed. In general, best practice is to give temporary access for three days. This will help if there are some delays (holidays), and order will be not verified automatically, so customer care have three days to fix it.
You may check access for a user by using the Check access API.
Verification of order
Verification is a process in the Importing application in the Connect subscription management system. The order data will be fully validated, followed by handling the instructions on the order. If automatic verification of order is not success, the order must be handled manually by customer care.
Modified at 2025-06-12 10:18:19