The technical bit...
When a transaction is processed using a server there are a number of fields that are sent from your website to ours.
One of these fields is account type.
The account type field can contain 3 values:
- E – for ecommerce transactions
- M – for telephone (MOTO) transactions
- C – for repeat transactions
The account type field is used to simply instruct Opayo which merchant number is going to be used to process the transaction.
Important – In order to send a value as M or C you must have the relevant merchant number active on your Opayo account.
In order to determine the type of transaction that is being processed you will need to include the account type field in your transaction registration post that is sent to us from your website/backend office system.
You can find out all of the information about the transaction registration post in the server protocol and integration guides on our website.
Alongside this you will also need to include all of the customer's details who will be processing the transaction – in order to do this you will need to build a form into your platform that will allow you to capture the customer's details prior to processing the transactions.
How you do this is entirely up to you, however. All Opayo requires is the details of the customer along with the account type field to be submitted to begin processing the transaction.
Processing the transaction
Now that you have included the account type field into your transaction registration post the payment will be able to be processed.
The difference between an ecommerce and MOTO transaction is that you or your staff will be entering the card details for the transaction on behalf of your customer. The customer will provide their card details to your over the phone.
As such you or your staff will be using the Opayo payment pages in place of your customer.
What will happen
If you are using a back-end office platform you will need to ensure the platform can support a post to the Opayo system and either re-direct to a browser (normal server) or support a browser window within the platform itself (server iframe).
For a normal server, you will see the card selection, card details, card confirmation, and authorisation pages when entering the details for your customer.