Q&A for order

In this article you may find tips & tricks for how to register an order.

Identify payer and receiver

Where can I find the payer and receiver object?
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.

When is the payer and receiver object required?
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.

The payer and receiver are the same person. Do I need to enter the same data twice?
No. The system will automatically recognize that the payer is the receiver if the receiver object is not defined.

Recurring payment and prepaid order

What is a recurring payment?
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.

What is a prepaid order?
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

We want to provide a specific payment method. What should I do?
You need to contact Mediaconnect 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.

Which payment methods support recurring payment and prepayment?
Some of the payment methods support recurring payment and prepayment. This information are described in the description for the Register order API in our API documentation.

I want to use a payment providers which is not supported by Mediaconnect. What should I do ?
If you want, you may implement your own integration with different payment providers so you may send order as prepaid. Also, you may use McPay to process the payment before the user registration and order registration. Such an order needs to be send as prepaid as well.

Choose productSpecType

I want to sell a single book. What type of productSpecType should I use?
All single products, which is not a subscription product, issue or article should use productSpecType product.

I want to sell a subscription product. What type of productSpecType should I use?
All subscription products should use productSpecType coupon.

I want to sell a single copy of a periodical magazine. What type of productSpecType should I use, and which fields is required?
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

The user initiate to register an order. May I do a payment before placing the order?

If your user register an order, then you may process the payment on that order. There are two options to do that:

• Easiest Integration (flow 1): Process payment after order is placed in Mediaconnect.
• Advanced Integration (flow 2): Do the payment before order registering with the Order API.

If you want to process the payment before registering order in Mediaconnect, please use your own integration to do the payment or you may use McPay that supports seamless view for payments. Then register order with the Order API as a prepaid order.

How to register order

There are two similar APIs for creating order. What are the differences between Register order and Register order - client mode?

The difference is whether the user is logged into the system before order registration. The user needs to be logged into the system for using the Register order API. You may register an order without user interaction by using the Register order - client mode API.

I have registered an order. What is the next step?
You have a to fulfill the order by using fulfillment API or fulfillment URL.

There are two alternatives to fulfill an order. What is the difference between fulfillment API and fulfillment URL?
You should use fulfillment URL if the order is not prepaid and fulfillment API if the order is prepaid.

I have fulfilled the order. Is everything done now?
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

What does Assign user - client mode API do?
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.

Based on the information in response from the API, you may redirect to login page URL for existing user or resetPassword URL for new users.

A user account will be created if it does not exit from before. The system will send a message to the user's mobile number or email address. User may decide if he click URL in email or SMS and will be logged/verified automatically or will continue with process on order page to be redirected to article with paid content.

The API may also be used to check if the user already has a ConnectID account. For more information, please read our API documentation.

Temporary access

How does temporary access work?
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.

How do I check access for a user?
You may check access for a user by using the Check access API.

Verification of order

How is the verification process for the 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.