support
Back to documentation
Search
Categories
Tags
main parametersexpand all
paymentMethodToken
required
currency
required
orderId
recommended
information about your customer
customer
reference
recommended
email
required
billingDetails
title
category
firstName
lastName
phoneNumber
streetNumber
address
address2
district
zipCode
city
state
country
language
cellPhoneNumber
identityCode
identityType
legalName
shippingDetails
category
firstName
lastName
phoneNumber
streetNumber
address
address2
district
zipCode
city
state
country
deliveryCompanyName
shippingSpeed
shippingMethod
legalName
identityCode
shoppingCart
insuranceAmount
shippingAmount
taxAmount
cartItemInfo
[1]
productLabel
productType
productRef
productQty
productAmount
productVat
ipAddress
general transaction options
contrib
ipnTargetUrl
fingerPrintId
card related options
transactionOptions
cardOptions
paymentSource
mid
retry
Try me
Documentation

Token/Update web service

POSThttps://api.systempay.fr/api-payment/V4/Token/Update

The Token/Update operation is a REST API web service.

It allows you to update the card attached to a token (paymentMethodToken).

Updating a token using a new card

You can update a token using an embedded form.

In this case, the Token/Update REST web service will return a formToken that must be used with our JavaScript form.

The token update operation is similar to creation. All you need to do is pass the paymentMethodToken that you want to update.

A transaction of 1 EUR (or 0.00 EUR if the acquirer supports it) is created along with the token. The token will be inside the Transaction object, in the paymentMethodToken parameter.

To see the reference documentation of the response containing the formToken, go to: Charge/PaymentForm.

If you are PCI-DSS certified

If you are PCI DSS certified, you can transmit sensitive information (such as card number) directly to the web service. For more information, go to our page dedicated to using the Token/Update REST web service in PCI DSS mode.

Request parameters

The Token/Update REST web service supports the following parameters:

paymentMethodToken

Token associated with a payment method.

Only tokens associated with a credit card are supported.

Format

currency

Payment currency. Alphabetic code in uppercase according to alpha-3 (ISO 4217).

Eg: "EUR" for the euro.

Format

Possible values

The possible values are:

Currency ISO 4217 ENCODING Fractional unit
Australian dollar (036) AUD 2
Lev Bulgare (975) BGN 2
Brazilian real (986) BRL 2
Canadian dollar (124) CAD 2
Swiss franc (756) CHF 2
Chinese renminbi (156) CNY 1
Czech koruna (203) CZK 2
Danish crown (208) DKK 2
Euro (978) EUR 2
Pound Sterling (826) GBP 2
Hong Kong dollar (344) HKD 2
Kuna Croate (191) HRK 2
Hungarian forint (348) HUF 2
Indian rupee (356) INR 2
Indonesian rupiah (360) IDR 2
Japanese yen (392) JPY 0
Cambodian riel (116) KHR 0
South Korean won (410) KRW 0
Mexican peso (484) MXN 2
Malaysian ringgit (458) MYR 2
New Zealand dollar (554) NZD 2
Norwegian crown (578) NOK 2
Philippine peso (608) PHP 2
Polish zloty (985) PLN 2
Leu Roumain (946) RON 2
Russian ruble (643) RUB 2
Singapore dollar (702) SGD 2
Swedish krona (752) SEK 2
Thai baht (764) THB 2
Turkish lira (949) TRY 2
New Taiwan dollar (901) TWD 2
US dollar (840) USD 2
CFP Franc (953) XPF 0
South African rand (710) ZAR 2

orderId

Order reference defined by the Merchant.Does not support UTF-8 characters.

Format

customer.reference

Buyer ID on the merchant side.

Format

customer.email

Buyer's e-mail address.

Format

customer.ipAddress

Buyer's IP address.

Format

address

Path: customer.billingDetails.address

Billing address.

Warning: the characters > and < are not authorized.

Format

address2

Path: customer.billingDetails.address2

Second line of the billing address.

Warning: the characters > and < are not authorized.

Format

category

Path: customer.billingDetails.category

Buyer type.

Format

Possible values

values Description
PRIVATE Individual buyer type.
COMPANY Company buyer type.

cellPhoneNumber

Path: customer.billingDetails.cellPhoneNumber

Buyer's cell phone number.

Accepts all formats:

Examples:

  • 0623456789
  • +33623456789
  • 0033623456789
  • (+34) 824 65 43 21
  • 87 77 12 34

Format

city

Path: customer.billingDetails.city

City of the billing address.

Format

country

Path: customer.billingDetails.country

Buyer's country (in uppercase, in accordance with the ISO 3166-1 alpha-2 country codes).

Format

Possible values

Examples of possible values:

Country Code
AUSTRIA AT
BRAZIL BR
CORSICA FR
IVORY COAST CI
FRANCE FR
GUADELOUPE GP
INDIA IN
MARTINIQUE MQ
NEW CALEDONIA NC
ST-PIERRE-ET-MIQUELON PM
FRENCH POLYNESIA PF

district

Path: customer.billingDetails.district

District of the billing address.

Format

firstName

Path: customer.billingDetails.firstName

Buyer's first name.

Format

identityCode

Path: customer.billingDetails.identityCode

National identifier. Allows to identify each citizen within a country.

Format

identityType

Path: customer.billingDetails.identityType

ID type.

Possible values:

Type Description
DNI Documento Nacional de Identidad
CC Cédula de ciudadania
TI Tarjeta de Identidad
CE Cédula de Extranjeria
NI Número de Identificación Tributaria
PS Pasaporte

Format

language

Path: customer.billingDetails.language

Buyer's language code, according to ISO 639-1.

Specify the language in which payment confirmation e-mails are sent.

Format

Possible values

Examples of possible values:

Language Code
German (Germany) DE
English (United Kingdom) EN
English (United States) EN
Chinese (Traditional) ZH
Spanish (Spain) ES
Spanish (Chile) ES
French (France) FR
Italian (Italy) IT
Japanese (Japan) JP
Dutch (the Netherlands) NL
Polish (Poland) PL
Portuguese (Brazil) PT
Portuguese (Portugal) PT
Russian (Russia) RU

lastName

Path: customer.billingDetails.lastName

Buyer's last name.

Format

legalName

Path: customer.billingDetails.legalName

Legal name.

Format

phoneNumber

Path: customer.billingDetails.phoneNumber

Buyer's phone number.

Accepts all formats:

Examples:

  • 0123456789
  • +33123456789
  • 0033123456789
  • (00.571) 638.14.00
  • 40 41 42 42

Format

state

Path: customer.billingDetails.state

Region (state) of the billing address. It is recommended, but not mandatory, to pass the value in ISO-3166-2.

Format

streetNumber

Path: customer.billingDetails.streetNumber

Street number of the billing address.

Accepted characters:

  • Alphabetical characters (from "A" to "Z" and from "a" to "z")
  • Space

Format

title

Path: customer.billingDetails.title

Buyer's title.

Examples:

  • Mr
  • Ms.
  • Mrs

Format

zipCode

Path: customer.billingDetails.zipCode

Zip code of the billing address.

Format

address

Path: customer.shippingDetails.address

Shipping address.

Warning: the characters > and < are not authorized.

Format

address2

Path: customer.shippingDetails.address2

Second line of the shipping address.

Warning: the characters > and < are not authorized.

Format

category

Path: customer.shippingDetails.category

Buyer type.

Format

Possible values

values Description
PRIVATE Individual buyer type.
COMPANY Company buyer type.

city

Path: customer.shippingDetails.city

Shipping city.

Format

country

Path: customer.shippingDetails.country

Shipping country (in uppercase, in accordance with the ISO 3166-1 alpha-2 country codes).

Format

Possible values

Examples of possible values:

Country Code
AUSTRIA AT
BRAZIL BR
CORSICA FR
IVORY COAST CI
FRANCE FR
GUADELOUPE GP
INDIA IN
MARTINIQUE MQ
NEW CALEDONIA NC
ST-PIERRE-ET-MIQUELON PM
FRENCH POLYNESIA PF

deliveryCompanyName

Path: customer.shippingDetails.deliveryCompanyName

Name of the delivery company.

Format

district

Path: customer.shippingDetails.district

District of the billing address.

Format

firstName

Path: customer.shippingDetails.firstName

First name of the recipient.

Format

identityCode

Path: customer.shippingDetails.identityCode

National identifier. Allows to identify each citizen within a country.

Format

lastName

Path: customer.shippingDetails.lastName

Buyer's last name.

Format

legalName

Path: customer.shippingDetails.legalName

Legal name in case of shipping to a company.

Format

phoneNumber

Path: customer.shippingDetails.phoneNumber

Buyer's phone number.

Accepts all formats:

Examples:

  • 0123456789
  • +33123456789
  • 0033123456789
  • (00.571) 638.14.00
  • 40 41 42 42

Format

shippingMethod

Path: customer.shippingDetails.shippingMethod

Shipping mode.

Format

Possible values

Value Description
RECLAIM_IN_SHOP Item pickup at the shop.
RELAY_POINT Use of a third-party pickup network (Kiala, Alveol, etc.).
RECLAIM_IN_STATION Pickup at an airport, a train station or a travel agency.
PACKAGE_DELIVERY_COMPANY Shipping by the transporter (Colissimo, UPS, etc.).
ETICKET Issue of an electronic ticket, online download of the product.
CARD_HOLDER_ADDRESS Delivery to the buyer. Reserved for future use.
VERIFIED_ADDRESS Delivery to a verified address.Reserved for future use.
NOT_VERIFIED_ADDRESS Delivery to a non-verified address.Reserved for future use.
SHIP_TO_STORE In-store pickup.Reserved for future use.
DIGITAL_GOOD Digital delivery.Reserved for future use.
ETRAVEL_OR_ETICKET E-ticket.Reserved for future use.
OTHER Other: Reserved for future use.
PICKUP_POINT Pickup point delivery.Reserved for future use.
AUTOMATED_PICKUP_POINT Pickup at an automatic pickup point.Reserved for future use.

shippingSpeed

Path: customer.shippingDetails.shippingSpeed

Shipping delay.

Format

Possible values

Examples of possible values:

Value Description
STANDARD Standard shipping.
EXPRESS Express shipping (in less than 24h).
PRIORITY Priority shipping (Click & Collect).

state

Path: customer.shippingDetails.state

Region of the billing address.

Format

streetNumber

Path: customer.shippingDetails.streetNumber

Street number of the delivery address.

Accepted characters:

  • Alphabetical characters (from "A" to "Z" and from "a" to "z")
  • Space

Format

zipCode

Path: customer.shippingDetails.zipCode

Zip code of the billing address.

Format

insuranceAmount

Path: customer.shoppingCart.insuranceAmount

Insurance amount for the entire order, expressed in the smallest monetary unit (cent for euro).

Example: 30050 for EUR 300.50.

Format

shippingAmount

Path: customer.shoppingCart.shippingAmount

Amount of delivery fees for the entire order, expressed in its smallest monetary unit (cent for euro).

Example: 30050 for EUR 300.50.

Format

taxAmount

Path: customer.shoppingCart.taxAmount

Amount of taxes for the entire order expressed in the smallest monetary unit (cent for euro).

Example: 30050 for EUR 300.50.

Format

cartItemInfo

Path: customer.shoppingCart.cartItemInfo

cardItemInfo is a list that contains Customer/ShoppingCartItemInfo objects.

It allows you to describe each item in the cart.

Format

productAmount

Path: customer.shoppingCart.cartItemInfo.productAmount

Amount of the product expressed in the smallest currency unit (cent for euro).

Example: 30050 for EUR 300.50.

Format

productLabel

Path: customer.shoppingCart.cartItemInfo.productLabel

Product name.

Format

productQty

Path: customer.shoppingCart.cartItemInfo.productQty

Product quantity.

Format

productRef

Path: customer.shoppingCart.cartItemInfo.productRef

Product reference.

Format

productType

Path: customer.shoppingCart.cartItemInfo.productType

Product type.

Possible values

Value Description
FOOD_AND_GROCERY Food and grocery
AUTOMOTIVE Cars / Moto
ENTERTAINMENT Entertainment / Culture
HOME_AND_GARDEN Home and gardening
HOME_APPLIANCE Household appliances
AUCTION_AND_GROUP_BUYING Auctions and group purchasing
FLOWERS_AND_GIFTS Flowers and presents
COMPUTER_AND_SOFTWARE Computers and software
HEALTH_AND_BEAUTY Health and beauty
SERVICE_FOR_INDIVIDUAL Services for individuals
SERVICE_FOR_BUSINESS Services for companies
SPORTS Sports
CLOTHING_AND_ACCESSORIES Clothes and accessories
TRAVEL Travel
HOME_AUDIO_PHOTO_VIDEO Sound, image and video
TELEPHONY Telephony

Format

productVat

Path: customer.shoppingCart.cartItemInfo.productVat

Product type.

Tax fee amount (expressed in the smallest currency unit).

Possible values

Value Description
Integer Transaction amount. Its value must be a positive integer (e.g.: 1234 for 12.34 EUR).
Decimal number, lower than 100 Percentage applied to the amount. Examples: 20.0 or 19.6532

To display a percentage applied to the payment amount for the product in question, the value should have maximum 4 digits after the decimal point. The decimal separator is mandatory for displaying a percentage. The decimal separator is represented by the "." symbol.

Format

contrib

Name of the e-commerce solution used on the merchant website and its version number.

Format

ipnTargetUrl

You can override the Instant Payment Notification (also called IPN) in the payment form in case you use one shop for various sales channels, payment types, languages, etc.

Format

fingerPrintId

This field is used by merchants who implement the risk analyzer in their payment page. Allows you to send the session ID (or fingerPrint Id) to the payment platform to finalize the risk analysis.

The supported analyzers are:

  • NOTO
  • Cybersource
  • MonitorPlus
  • ClearSale

Can contain uppercase and lowercase characters, numbers or hyphens ([A-Z] [a-z], 0-9, _, -).

Format

mid

Path: transactionOptions.cardOptions.mid

Merchant ID number. If this field is populated, make sure you use the appropriate MID depending on the card scheme.

Format

paymentSource

Path: transactionOptions.cardOptions.paymentSource

Payment source.

Format

Possible values

The possible values are:

Value Description
EC E-Commerce: the data of the means of payment are entered by the buyer. This value allows a strong authentication during the payment.
MOTO MAIL OR TELEPHONE ORDER: entry by an operator.The payment information is sent by mail or e-mail. Requires a VAD contract.
CC Call Center: payment made through a call center. Requires a VAD contract.
OTHER Other sales channel.Returned output value for payments made via the Merchant Back Office, payments by file, recurring payments, proximity payments.
Absent ou null The default value is "EC".

retry

Path: transactionOptions.cardOptions.retry

Number of new attempts available in case the payment is rejected (3 by default).

Format

Response reference

Response Context
Charge/PaymentForm Object containing a hash that should be used with the embedded form to create a new transaction.

See the reference of each response for more information.