Handleiding voor instellingen van uw ordersysteem

De te volgen stappen:

  1. Registreer de locatie van uw orderpagina
  2. Het inrichten van uw orderpagina
    1. vereiste form variabelen
    2. optioneleoptionele variabelen
    3. automatische incasso (rebilling)
    4. Klantgegevens van de creditcard houder posten (optioneel)
    5. voorbeeld code
    6. order processing API
    7. Rebill update API
    8. Refund API
  3. Instellen van Page ID in het Merchant Menu
    1. Sending customers back to your server
    2. silent post
    3. multiple languages
    4. multiple currencies
    5. pincodes, username/passwords
  4. Instant Payment Notifications
    1. difference between silent post and IPN
  5. Configure Password Links
  6. Run a test order
  7. Contact our technical helpdesk

Stap 1: Registreer de locatie van uw orderpagina's

De locatie van uw orderpagina's

Plaatsing op de MultiCards Servers
 Uw account is inclusief 4 gratis web orderpagina's op onze secure server. Deze ruimte kan tevens gebruikt voor de vereiste graphics.

Plaatsing op uw eigen server
Natuurlijk is ook mogelijk de orderpagina's op uw eigen server te plaatsen. Voor de eerste stap in het order proces heeft u geen ssl certificaat nodig, omdat er hier geen credit card gegevens worden ingevoerd.

Registratie van de locatie van uw orderpagina's 

Om veiligheidsredenen dienen alle orderpagina's geregistreerd worden in de sectie order pages van het Merchant Menu. Login in uw Merchant Menu en klik op de order page knop om de locatie van uw orderpagina's in te voeren, dit zijn de z.g, Page ID's 

Nieuwe order pagina's toevoegen
Gebruik de optie "'New Order Page" knop om een nieuwe Page Id aan te maken. Alleen MultiCards account afdeling mag de locatie van uw bestaande order pagina locatie op uw verzoek aanpassen.

Aanpassen van de locatie van de order pagina voor bestaande Page ID
Stuur een support ticket met het page ID nummer en de nieuwe order pagina locatie. De nieuwe pagina moet worden goedgekeurd door onze afdelinge Risico Beheer. Normaal gesproken zal dit binnen 24 uur gebeuren.

 

Stap 2: Het inrichten van uw orderpagina 

Zodra de  locatie van uw orderpagina is ingesteld in de order page sectie van het Merchant Menu, kunt u de orderpagina's in HTML code maken met de benodigde "form variabelen" zoals verderop wordt besproken.  Neem contact op met onze technische afdeling voor gratis ondersteuning als u op dit punt vragen heeft!

Shopping cart Systemen

.Een shopping cart wordt meestal gebruikt als u veel producten moet beheren, zoals meer dan 25.

Ondersteunde  shopping carts

Onze technische afdeling kan u hulp bieden!!
Onze technische afdeling kan u alleen assisteren met het aanpassen van de  html code  en vereiste variabelen van uw orderpagina op uw eigen server als u FTP toegang op uw server kan geven. Voor sommige bedrijfsmodellen kunnen wij een order pagina met locatie op onze MultiCards servers verplicht stellen.

Het posten van de variabelen naar de MultiCards server
 Een order pagina bevat een post commando met de vereiste en toegestane MultiCards variabelen (waarden). De variabelen moeten gepost worden naar een specifieke URL op onze secure server.

<form action=https://secure.multicards.com/cgi-bin/order2/processorder1.pl method="post">

Vereiste "form variables"

name= type= value=
mer_id hidden Your 6 digit merchant number.
mer_url_idx hidden Refers to the page ID (page properties) in the MultiCards database. Every order page should have it's own idx number. You can create new page ID's in the Merchant Menu.
item1_desc
item2_desc
etc...
hidden Short description of product.
item1_price
item2_price
etc...
hidden Price of product in format xxx.yy, ie. 23.80.
item1_qty
item2_qty
etc...
text or
hidden
Quantity of product in integer format ie. 4.

Hier is een voorbeeld:

<form action="https://secure.multicards.com/cgi-bin/order2/processorder1.pl" method="post">
<input name="mer_id" value="xxxxxx" type="hidden"> <!--your merchant number -->
<input name="mer_url_idx" value="1" type="hidden"> <!-- the page id number -->

<input name="item1_desc" value="Sample product 1" type="hidden">
<input name="item1_price" value="50.00" type="hidden">
<input name="item1_qty" type="text" size="3" maxlength="2">

<input name="item2_desc" value="Sample product 2" type="hidden">
<input name="item2_price" value="100.00" type="hidden">
<input name="item2_qty" type="text" size="3" maxlength="2">

<input name="submit" type="submit" value="Proceed to Secure Payment Server">
</form>

BELANGRIJK
Let erop, dat het niet is toegestaan open waarden te gebruiken voor product omschrijving en de prijs van het product. Alle prijzen en omschrijvingen moeten vaststaan of uit een database worden opgehaald.

Optionele  "variables"

name= value=
user1
user2
etc...
Met deze variabelen kunt u extra informatie posten. De userX (user1, user2 etc) variable is de enige toegestane variabele om andere  invoer velden te gebruiken. Alle andere variable namen worden niet ondersteund, bijvoorbeeld userX, userY, input1
sales_tax_factor Tax, value=0.10 for 10% sales tax.
sales_tax_exclude Tax exclude, value=10 to exclude item10, or value=10,11 to exclude item 10 and 11 from taxation.
sales_discount_factor Discount, value=0.10 for 10% discount.
sales_discount_exclude Discount exclude, value=10 to exclude item10, or value=10,11 to exclude item 10 and 11 from discount.
sales_discount_amount Discount amount, value=19.99 to discount 19.99.

Automatische incasso z.g recurring billing (optioneel)

De optie automatische incasso of recurring billing is een klantvriendelijke manier om een credit card van een klant te herbelasten met diens toestemming. De klant heeft volledige beheersrechten over de herbelasting met het order nummer en zijn paswoord om de incasso te starten of te stoppen en/of wijzigingen aan te brengen zoals frequentie, adres, postcode en vervaldatum van de creditcard.  

 De MultiCards merchant heeft toegang tot individuele orders om de frequentie en of te belasten bedragen aan te passen, uiteraard in overleg met de klant. Dit is gemakkelijk als prijzen zijn gewijzigd, bijvoorbeeld door btw verhoging e.d. De automatische incasso of rebilling werkt met alle ondersteunde valuta. Merchants kunnen de rebillings aanpassen via de rebilling link in het Merchant Menu. De variablen in een orderpagina die dit bewerkstelligen zijn: 

Variable Value explained
rebill_type

[frequency]-[amount]-[days]

Where Frequency is:

  • monthly
  • quarterly
  • sixmonthly
  • yearly

Where Amount is: rebill amount in format 0.00

Where Days is: Number of days to start first rebilling after initial transaction. When empty default value for monthly rebillings is 30 and for quarterly rebillings 90 days.

rebill_count Total number of rebillings. Default is unlimited.
rebill_password Password for customer to login to transaction. When empty
the password is generated automatically.
rebill_desc Product description in all rebilling transactions. When empty
the description is "rebilling for order xxxxxx.yyyyyyy".

Voorbeeld code voor een periodieke incasso

:Hierna volgt een voorbeeld voor code van een maandelijkse incasso voor USD 19.99 die start na 14 dagen  met een eerste betaling bij plaatsing van de order voor USD 9.99

<form action="https://secure.multicards.com/cgi-bin/order2/processorder1.pl" method="post">
<input name="mer_id" value="xxxxxx" type="hidden"> <!--your merchant number -->
<input name="mer_url_idx" value="1" type="hidden"> <!-- the page id number -->

<input name="item1_desc" value="14 days trial" type="hidden">
<input name="item1_price" value="9.99" type="hidden">
<input name="item1_qty" type="hidden" value="1">

<input type="hidden" name="rebill_type" value="monthly-19.99-14">

<input name="submit" type="submit" value="Proceed to Secure Payment Server">
</form>

Klantgegevens van de creditcard houder posten (optioneel)

Standaard wordt vanaf de order pagina slechts product info en prijs naar de MultiCards server gepost. Op het eerste MultiCards scherm wordt de klant dan gevraagd het land van de credit card en het kaart type te selecteren. Het tweede MultiCards scherm vraagt de klant de verdere contact gegevens van de credit card houder.

U mag en kan  de eerste 2 MultiCards schermen overslaan

Indien u de klantgegevens al gevraagd hebt en opgeslagen in uw database kunt u de eerste 2 schermen overslaan door alle vereiste variabelen ineens te posten door gebruik te maken van de variabele next_phase.  Het MultiCards scherm dat de klant dan het eerste ziet is het scherm om credit card nummer en vervaldatum in te voeren. U mag deze laatste gegevens nooit naar de MultiCards server posten. Dat is alleen mogelijk met een machtiging van MultiCards met een API interface.

De variabelen voor klantgegevens van creditcard houder mee posten

Variable Value
next_phase Use value "paydata" to go directly to the credit card fields page
cust_country The country name in ISO format
pay_method_type Use one of the following values: creditcard_visa, creditcard_mastercard, creditcard_eurocard, creditcard_americanexpress, creditcard_discover, creditcard_dinersclub, creditcard_carteblanche, creditcard_jcb, bank_directdebit, bank_ideal
cust_name The customer name
cust_company The company name
info1 Delivery/Mail/Business Address
cust_phone Customer phone number
cust_fax Customer fax number
cust_email Customer e-mail address
cust_address1 Cardholder address
cust_zip Cardholder zipcode
cust_city Cardholder city
cust_state Cardholder state

Voorbeeld van  html code

U kunt een voorbeeldpagina downloaden met alle vereiste en mogelijke variabelen in een orderpagina door op de link hierna  te klikken.  download example html code 

De onderstaande sectie betreffende onze API is bedoeld voor gevorderden. Wij handhaven deze in het engels, omdat hier verdere technische kennis en machtiging voor nodig is. Voor normaal gebruik heeft u dit niet nodig. U kunt verder gaan met stap 3.

Order processing API (optional)

Another option to post the order details is using our order processing API. This option is only available for:

  • PCI DSS compliant merchants
  • Merchants with a direct merchant account with our acquiring bank

Contact our Accounts Department for a complete overview of all requirements for this option and availability for your account.

Extra variables for order processing API
The API uses exactly the same variables as our normal processing interface, but including:

  • card_num
  • card_name
  • card_code 
  • card_exp (mm/yy)

The location of the API processing script will be provided once your account has been approved.

API response codes:

Variable name: Value:
response_code 1 = accepted
2 = declined
3 = error
response_text descriptive text of response code, i.e. InputError, Declined, Accepted.
error In case of an error response, error contains one or more reasons why the post data was rejected.
order_num In case of an accepted response, the MultiCards order number is returned.
billing_name Very important: The name that will appear on the customers credit card statements.

Rebill update API (optional)

To stop, restart, or change the amount for existing rebilling transactions via the MultiCards Gateway, the following parameters should be posted to the secure script under SSL.

The location of the API rebill script will be provided once this feature has been activated for your account.

Input parameters:

Name
Type
Example Value
Notes
MerchantID
TEXT
070167
Your 6 digit merchant number
password
TEXT
huj%t678
As directed by MultiCards.
action
TEXT
rebill.stop, rebill.start, rebill.changeamount
Stop existing rebilling, restart existing inactive rebilling, change amount to be rebilled in next period for specified order number.
ordernumber
TEXT
070167.3234567
MultiCards order number.
amount
TEXT
10.05
New rebill amount (only for action rebill.changeamount).

Response parameters:

Name
Type
Example Value
Notes
response_code
TEXT
000, 001, 002, 003, 004, 100, 101, 300, 301, or 302
000 = success,
001 = unknown or invalid MerchantID,
002 = password incorrect,
003 = service has not been enabled for this merchant,
004 = action parameter incorrect,
005 = this IP is not in the allowed list (IP=$remote),
100= Invalid or unknown order number,
101= No rebilling was found for this order number,
300 = rebilling already stopped,
301 = rebilling already started,
302 = invalid amount passed (only for action rebill.changeamount).
600 = error – contact support.
response_text
TEXT
Success, Unknown or invalid MerchantID, …
Descriptive text for the response code. Will repeat for each response as necessary.

Refund API

To issue a refund for an existing transaction via the MultiCards Gateway, the following parameters should be posted to the secure script under SSL.

Secure Script Location: https://secure.multicards.com/cgi-bin/auto/crauto.cgi

Refund Transaction API input parameters:

Name
Type
Example Value
Notes
merchantid
TEXT
070167
Your 6 digit merchant number.
password
TEXT
huj%t678
As directed by MultiCards.
action
TEXT
credit, partial.credit
Full credit, or partial credit.
reason
TEXT
Customer requested refund, Duplicate transaction placed in error, …
Descriptive text of reason for refund.
trans_id
TEXT
745677789
As output previously by the debit transaction script.
amount
TEXT
10.05
Only for action = partial.credit. Cannot exceed original debit amount.

 Refund Transaction API response parameters:

Name
Type
Example Value
Notes
response_code
TEXT
000, 001, 002, 003, 004, 100, 300, 301, or 302
000 = success, 001 = unknown or invalid MerchantID, 002 = password incorrect, 003 = service has not been enabled for this merchant, 004 = action parameter incorrect, 100= Invalid or unknown transaction id, 300 = transaction already refunded, 301 = transaction refund pending, 302 = invalid amount passed (only for action partial.credit).
response_text
TEXT
Success, Unknown or invalid MerchantID, …
Descriptive text for the response code. Will repeat for each response as necessary.

 

 

Stap 3: Instellen van Page ID in het Merchant Menu

IIn de order page sectie van het Merchant Menu klikt u op de icoon voor de instellingen.Vul alle gegevens in en controleer ze.
Property Explanation
Name De naam van uw bedrijf. Deze naam wordt gebruikt in de MultiCards schermen en orderbevestiging.
Website location

De exacte locatie URL van uw website. Aleen onze account afdeling mag deze waarde aanpassen die overeenkomt met de door ons geaccepteerde website. De locatie wordt weergegeven op de MultiCards schermen en orderbevestiging

Allowed order page location

Een Page ID kan alleen worden gekoppeld aan een door MultiCards geaccepteerde order pagina locatie. Dit kan een statische orderpagina zijn (.html) of een dynamische orderpagina (.php .asp etc). Orders gepost van een niet-correct ingestelde orderpagina locatie worden niet toegestaan door het systeem en de merchant ontvangt een email alert.

Successful transaction return location (PostURL) De website locatie waar naar de klant moet worden doorgestuurd na een succesvolle betaling.
Post fields Geef de variabelen op die gepost moeten naar een script op uw ebsite met de post  "Continue page location".

bijvoorbeeld (zonder spaties, met komma gescheiden):
order_num,total_amount,item1_qty,cust_name
Continue button Label  Wijzig de tekst van de knop op de afsluitpagina. De standaard waarde is "proceed to"
Continue Button Force Press Indien geaktiveerd, ontvangt de klant een waarschuwing als de browser wordt gesloten zonder op de continue knop te drukken.
Order page e-mail Het email adres waar de email orderbevestiging naar toe wordt gestuurd. Dit adres wordt ook aan de klant gestuurd voor ondersteuning.
Custom message Deze tekst verschijnt in de afsluitpagina en email orderbevestiging.
Receipt page code Deze code wordt geplaatst in de HEAD sectie van de afsluitpagina (receipt page) en kan worden gebruikt voor een affiliate tracking code. MultiCards account afdeling kan de code voor u aanpassen.
Terms and Conditions Voeg uw eigen Verkoopvoorwaarden toe aan de MultiCards order processing schermen.
Refund Policy Voeg uw eigen Voorwaarden toe aan de MultiCards order processing schermen voor restituties.
Delivery Policy Add your own Delivery policy to the order processing screens.Voeg uw eigen Afleveringsvoorwaarden to aan de MultiCards order processing schermen.
Use Email Validation Code

When enabled the customer receives a code by e-mail. Without this code the customer can not place an order. This function is used to make sure that the customers e-mail address is valid.

Indien geactiveerd kan een order alleen geplaatst worden met een email klantcode. Zonder deze code kan de klant geen order plaatsen. Dit is ingebouwd om er zeker van te zijn dat het email adres van de klant geldig is.

Onze software is geheel in het engels geprogrammeerd. Vanwege mogelijk vertaal- en interpretatie verschillen handhaven wij de onderstaande tekst in het engels. De tekst is bedoeld voor technisch gevorderden. Voor standaard gebruik heeft u dit niet nodig. U kunt verder gaan met stap 6.  

Sending the customer back to your server

After a successful transaction the customer will be redirected back to the "Successful transaction return location (PostURL)" defined in the Page ID settings.

It is possible to add transaction variables to that URL. The field 'Postfields' can be used to post the allowed and accepted order page variables posted by the orderpage and also special processing variables such as: total_amount and order_num.

How do Postfields work?
The Successful transaction return location (PostURL) and post fields you defined in your page id settings are added to the order receipt page (the last page in the order process) in the following web form format:

 <form action="continue page location" method="post">
<input name="postfield1" value="field1 value" type="hidden">
<input name="postfield2" value="field2 value" type="hidden">
<input name="postfield3" value="field3 value" type="hidden">
.....
<input name="submit" type="submit" value="Continue button label">
</form>

Activate 'Silent Post'

What is silent post?
When silent post is enabled, the form is automatically submitted in the background by our server. The post result is included where normally the above form is located. The silent post function is mostly used to retrieve a dynamic message or webform from your server, and include it in the MultiCards receipt page.

How does silent post work
To use 'Silent Post' you need to include <!--success--> in the response of your script. If this is not found in the response, our server assumes that the post was not successful and displays an error message to the customer together with a retry button.

Is silent post safe?
Because the post is done in the background by our server the PostURL is hidden for the customer. This allows you to add an IP check to your script and use the silent post function to start a secure process on your server.

Here is an example:

A company sells online tickets. They post their ticket ID in the user1 variable. The PostURL with Silent Post enabled is used to display the button to print the ticket in the receipt page.

Two scripts are involved:

The PostURL contains a link to script A. This script A receives user1 and order_num. Because silent post is used script A can have an IP check. Only posts from the MultiCards server are allowed. This ensures that only MultiCards marks an 'ID' (set in user1) to be paid. Script A needs to mark the ID as paid and adds the order number and a unique pincode.

Script A responds with the following (this will be included in the receipt page):

<!--success-->
<form action="http://yourdomain.com/location_of_script_B" autocomplete="off">
<input type=hidden name=ticketid value="value_of_user1">
<input type=hidden name=pincode value="pincode_created_by_script_A">
<input type=submit name=submit value="Print ticket">
</form>

Script B is called by the customer and receives the user1 and pincode values. This script checks if script A has marked the ID as paid and if the pincode is valid. If not, the customer is trying to commit fraud.

Use multiple languages

The language for an order page is set in the langcode field of the Page ID properties. When multiple languages are required you can add this optional code to your order page:

<select name="langcode">
<option selected>English</option>
<option value="it">Italian</option>
<option value="es">Spanish</option>
<option value="nl">Dutch</option>
<option value="fr">French</option>
<option value="de">German</option>
<option value="ru">Russian</option>
</select>

Use multiple currencies

The default currency for an order page or shopping cart is set in the Page ID properties. It is possible to send the currency together with the other transaction details. Please note that this option needs to be enabled in the Page ID properties screen in the Merchant Menu. The variable name for the currency is: valuta_code.

An example:

<select name="valuta_code" >
<option value="EUR" selected>EUR</option>
<option value="AUD">AUD</option>
<option value="CAD">CAD</option>
<option value="CHF">CHF</option>
<option value="CYP">CYP</option>
<option value="DKK">DKK</option>
<option value="GBP">GBP</option>
<option value="HKD">HKD</option>
<option value="INR">INR</option>
<option value="ISK">ISK</option>
<option value="JPY">JPY</option>
<option value="NZD">NZD</option>
<option value="USD">USD</option>
</select>

Pincodes & username/passwords

The MultiCards server can dynamically generate pincodes and use a by the merchant supplied list of pincodes and login details. In the orderpages section of the merchant menu click on Pincodes.

Pincode type How it works
Numeric (7 digits) You can upload a list if 7 digit pincodes. Per transaction a pincode will be removed from the list.
Username / Password Works like the Numeric 7 digit pincodes, but now can contain any value. For example:
username: xxxxxx password: yyyyyy
Repeatable password This password is not deleted after use, hence is used by all customers.
Auto generated repeatable password Use the notation {D7}-{A1} to auto generate patterns, D=digit, A=letter

The pincode value can be used as a post field to be posted to the continue page location (see above).

Pre-authorization

This function is under construction. Contact our technicians for more information.

 

Step 4: Instant Payment Notifications (optional)

Notifications are messages that can be sent to a script, which allows your server to be automatically notified when a new order is placed, or when the status of an order changes. To prevent unnecessary delays in the order system itself due to timeouts, the notifications are not sent in realtime, they are stored in our database and processed later. The delay should under normal circumstances not be more than 5 minutes.

Configuration
To use this feature, login to the merchant menu and click on 'Order Pages'. Then use the link 'server notifications (IPN)'. The field 'ExtraFields' can be used to post the allowed and accepted order page variables posted by the orderpage and also special processing variables such as: total_amount and fraudscore.

Specification
A notification consists of a HTTP POST, containing the following fields:

Field:

Description:

password The password field can be used to secure the post and make sure it is being posted from the MultiCards server. A second security layer can be an IP filter.

order_num

Order number in 6.5 or 6.7 format

status

New order status, as follows:

  • accepted
  • creditrequested
  • credited
  • retrieval
  • chargeback
  • declined
  • redirected (to the customers bank to place the order)
  • suspended (a customer email copy bounced, and he/she has several days to correct this. If that doesn't happen the order is voided/credited, if it is corrected the order is accepted)
  • unknown (the order was batch processed (this might occur if the realtime system is unable to process the order), meaning that the status will be known after processing the batch (usually the next day). So once again, the status will be sent using a second notification containing declined/accepted)
  • voided
  • rebillactivated
  • rebilldeactivated
  • error

reason

Reason for status change (text, not strictly specified, for informative purposes only). Examples are:
New order created (with status of order, see B and C why this is necessary)
Order accepted (when an order was batch processed and accepted later)
Order rejected
Order voided
Order credited
Rebilling accepted
Rebilling failed

origin

Origin of order/change. Possible values are order, rebill or manual

trans_type

Transaction type. Possible values are debit, credit or other

pageid

PageID that generated the order/rebilling. This value corresponds to the ID of your order pages. By including this value, you can optionally use the same notification handler script on your server for all your order pages.

notifyid

Our internal unique id for this notification.

created

Date + time in YYYY-MM-DD HH:MM:SS format when notification was created

**

Variables used during the order process. For example: cust_email,cust_phone,,item1_qty.

Because the transaction is completed you can also use total_amount and total_amount_us as postfields.

Response code
Your script should respond with a 200 OK HTTP Status code, letting our handler know that your script received the notification. Please do not post back a large amount of content.

Difference between silent post and Instant Payment Notifications

Silent post:

Server notifications:

Post triggered by the customer's web browser on 'accepted order confirmation screen': manually by customer, or automatically with 'silent post'

Post triggered automatically by our server after 3 minutes

Only accepted orders

Accepted orders, declined orders, refunds, chargebacks, etc...

Visible to customer during order process

Done by our server in the background

Mostly used to display information to the customer

Mostly used to update a database

It is possible to use both systems at the same time.

 

Step 5: Configure Password Links (optional) 

The MultiCards PWLink© is a real-time online access verification system linked to a rebilling and password management sytem and is used to manage subscription based membership sites.
This is a script that allows customers automatic access to a password protected area on your site after a realtime order is approved.

After approval of a realtime order, from the receipt page, a customer is asked to enter a username and password, which are then submitted to a script on your website. This script updates a password file, giving the customer instant access.

The latest version of this software is now able to automatically disable users after a rebill failure, or if the order is voided. We have added a password maintenance facility in your merchant menu. Through this facility you can manually deactivate/reactivate passwords, delete passwords (temporary disabled though), and create custom passwords, which are not linked to any order.

Configuration

Step 1. Download the password script here.
Step 2. Install the password script in a directory on your website with execute permissions.
Step 3. Test the script by entering the script url in your browser. You should see a login form.
Step 4. Enter the authentication code you chose or was issued to you by MultiCards. A menu should appear. If it does not, there are several possibilities, refer to errors below.

Operation

The script is activated from the receipt page, after an order was accepted.

In the receipt page a small form is included, which the customer can use to submit a username and password to your server

If something goes wrong, the action taken depends on what went wrong. If the customer entered a wrong username or a username that already existed, an error is shown to the customer stating what was wrong, giving the customer the chance to fix it. If something went wrong that can not be fixed by the customer, the customer sees "Configuration error" and an email is sent to the merchant containing details of the error.

When a password has successfully been submitted, both the merchant and the customer will receive a confirmation email.

Setup a password controlled directory

To use the MultiCards MC-Access Password link you need to have .htaccess installed on the directory that you want to protect. If you don't know how that works on your server, you need to contact your server administrator and ask him to install this in the directory you want to protect and add one administrative user. He also needs to tell you the server path to the directory where the password file is stored. Please note that if you place the script in the directory where the password file is and activate the script, a techinfo button appears that allows you to find the correct server path.

Error messages

The following table lists the most common errors messages you may encounter, with possible solutions.

Code Reason
602 Authentication failure
The authentication code you submitted was incorrect. Please check the authentication in the script itself against the authentication code set in the page definition on the MultiCards server.
650 Password file not found
The location you specified for the password is incorrect.
651 Password file not readable
The password file doesn't have proper access permissions. In order for the web browser to be able to read it, it must have sufficient read permissions. These can be set using the chmod command. If you don't know how this works, you should contact your system administrator.
652 Password file not writable
The password file doesn't have proper access permissions. In order for the web browser to be able to write it, it must have sufficient write permissions. These can be set using the chmod command. If you don't know how this works, you should contact your system administrator.
653 Password file can not be created
The password file didn't exist, so the script tried to create it, but that didn't work. Please make sure the directory where you want to keep the password file has proper permissions, or create a password file yourself.
650 Password file not found
660 Password file may not be stored in web directory
If you see this error, you tried to put the password file inside the web directory. This is very bad, because this may enable visitors of your website to retrieve the password file. If you specifically want to do this or you protected the directory the password file is in (for instance with a password), you can set the variable check_webdir in the script to 0. This check will then be disabled.

 

 

Stap 6: Doe een test order

In het Merchant Menu gaat u naar de knop "Test order pagina". Stel een test creditcard code in en volg de instructies om een test order te plaatsen met een test creditcard.

 Stap 7: Neem contact op met onze technische helpdesk

Indien u klaar bent, kunt U contact opnemen om de orderpagina te laten nakijken en activeren.

U kunt in alle gevallen overigens altijd onze hulp inroepen, stuur ons een bericht via een support ticket in het Merchant Menu!!