This API is available only by separate agreement

USING A FINNISH PERSONAL ID TO CREATE A NEW INVOICE

Calling Payment API

REQUEST:

The V4 interface is used in a server-to-server type fashion. The web store transfers the payment data directly as an HTTP POST -request. The web store can choose which http client product to use for this.

TEST: http://test1.maksuturva.fi/NewChargeWithTokenActionExtended.pmt

PRODUCTION: https://payments.maksuturva.fi/NewChargeWithTokenActionExtended.pmt

The general instructions for the payment interface are here.
Please note that all mandatory parameters in the generic V4 payment API are also mandatory in S2S invoice.

In the request, the version information and pre-selected payment method should have the following values in the interface information:

pmt_version = 4204
pmt_paymentmethod = FI70 or FIIN
pmt_token = < the Finnish personal ID of buyer/invoice recipient >
pmt_invoicedistributionmethod = EMAIL / POST

Skip to contents in this page

1 USING A FINNISH PERSONAL ID TO CREATE A NEW INVOICE
- 1.1 Calling Payment API
  - 1.1.1 REQUEST:
  - 1.1.2 RESPONSE:
- 1.2 Example scenarios and responses
- 1.3 Status query for Invoice payment
  - 1.3.1 Example
- 1.4 Testing

RESPONSE:

Example of an OK response:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<chargeWithTokenResponse>
    <pmt_action>NEW_PAYMENT_EXTENDED</pmt_action>
    <pmt_version>4204</pmt_version>
    <pmt_id>100000169</pmt_id>
    <pmt_reference>00000000001000002696</pmt_reference>
    <pmt_amount>50,00</pmt_amount>
    <pmt_currency>EUR</pmt_currency>
    <pmt_sellercosts>5,00</pmt_sellercosts>
    <pmt_paymentmethod>FI70</pmt_paymentmethod>
    <pmt_escrow>Y</pmt_escrow>
    <pmt_resultcode>00</pmt_resultcode>
</chargeWithTokenResponse>

Example of an error response:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<chargeWithTokenResponse>
  <pmt_resultcode>99</pmt_resultcode>
  <error name="pmt_userlocale" type="field">pmt_userlocale is invalid</error>
</chargeWithTokenResponse>

Possible result codes (pmt_resultcode) are:

00 = success

99 = fail

Error codes (pmt_errorcode) for a charge made with a token or for a status query:

ALREADY_PAID                           = Order has already been paid

ERROR                                  = Unknown error

ERROR_IN_PAYMENT                       = Error in processing of payment

ERROR_IN_REQUEST_PAYER_DATA            = Error(s) in information that can be edited by buyer 

ERROR_IN_REQUEST_TECHNICAL_DATA        = Error(s) in the technical data of the payment 

ERROR_PAYMENT_INSTRUMENT_LIMIT_EXCEEDED= The limit for the given payment instrument is exceeded

ERROR_PAYMENT_INSTRUMENT_NOT_FOUND     = The given payment instrument can not be found

ERROR_PAYMENT_METHOD_NOT_AVAILABLE     = The payment method chosen in the web store was not allowed

EXTERNAL_SERVICE_DENIED                = The chosen payment service denied the transaction

EXTERNAL_SERVICE_ERROR                 = The chosen payment service gave an error response

WAITING                                = Waiting for information on possible payment

Example scenarios and responses

When credit can not be approved:

Buyer’s social security number (pmt_token) is missing or null:

Buyer’s social security number (pmt_token) is erroneous:

Buyer’s email address is missing:

Buyer’s email address is erroneous:

Buyer’s address is missing:

Delivery address is missing:

Buyer’s postal code is missing or erroneous:

Delivery postal code is missing or erroneous:

Status query for Invoice payment

Version 0005 of Svea Payments’ Status Query interface can be used for the status query of tokenized payments or recurring payments made with tokens. General instructions can be found in here.

TEST: https://test1.maksuturva.fi/PaymentStatusQuery.pmt

PRODUCTION: https://payments.maksuturva.fi/PaymentStatusQuery.pmt

Example

Here is an example of a situation, where tokenization and payment has been performed, settlement of the transaction has been made to the web store and lastly, a status query has been done:

Testing

This API can be tested in Svea Payments customer test environment (http://test1.maksuturva.fi) with individual test credentials.

Please see TESTING for instructions on the authentication of payments made in test environment.