About Instanea

General information about Instanea


Logo

Info

Instanea is an acceptance solution based on payment initiation as defined by PSD2, which allows you to receive instant transfers.

Through this solution, your company and your customers benefit from all the advantages of instant transfers:

  • Speed: Transfer executed in less than 10 seconds with immediate availability of funds.
  • Convenience: 24/7 availability all year round and notification to the payor in the event of rejection of the transaction.
  • Ease: Choice of the reference of the transfer, allowing you to make an automatic reconciliation
  • Secure payment: no risk of chargeback with SEPA Instant

…And a simple user journey for your customers.

Whether for in-store sales or online on your website, the Instanea user experience is fluid and secure.

 

Use cases

Supported use cases

Supported interface

Use case

Description

Simple process

S-2-S

HPP

Authorization + Capture

Merchant wants to authorize payment and capture on delivery

  • not supported

  • use "Sale" instead to authorize and capture a payment within one step.


Sale (one-shot)

Merchant wants to collect money from customer via Instanea

  • Merchant's shop initiates Instanea payment request and receives URL to Instanea

  • Merchant redirects customer to Instanea URL

  • Customer enters bank account data (IBAN) and his name (account holder name) and confirms payment

  • Merchant's shop gets a notification about successful payment

(tick)


full or partial Credit

Merchant wants to credit some money back to customer after a payment has been successfully completed

  • not supported



full or partial Reversal

Merchant wants to cancel a payment which has not been completed

  • not supported



Process flow chart

Instanea process flow


interface


Calling the Instanea interface

To process a payment with online transfer with Instanea, call up the following URL:

https://paymentpage.axepta.bnpparibas/instanea.aspx


Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...

KeyFormatCNDDescription

MerchantID

ans..30

M

MerchantID, assigned by . Additionally this parameter has to be passed in plain language too.

KeyFormatCNDDescription
TransID

ans..64

MTransactionID provided by you which should be unique for each payment

Key

Format

CND

Description

Beschreibung

RefNr

an..18

M

Reference is mandatory and must be unique for each payment, allowed characters: A..Za..z0..9.


The format depends on the available paymethods for your MerchantId and this parameter is the end to end reference for the payment methods.

We advise to choose a format that could be used for all paymethods implemented on your website.

We strongly recommend to use the most restrictive format for this parameter (AN12 - M) and create unique RefNr.

More details : Data reconciliation : Key Data

This field is the 'End to End ID'.

The RefNr must be unique for Instanea Payment (End to End ID).

If the merchant sends the same RefNr twice, the second transaction will be blocked.

Die Referenznummer des Zahlungsvorganges. Sie muss eindeutig und einmalig sein und darf nur aus folgenden Zeichen bestehen: A..Za..z0..9

KeyFormatCNDDescription
Amount

n..10

M

Amount in the smallest currency unit (e.g. EUR Cent). Please contact the , if you want to capture amounts <100 (smallest currency unit).

KeyFormatCNDDescription
Currency

a3

M

Currency, three digits DIN / ISO 4217, e.g. EUR, USD, GBP. Please find an overview here: Currency table

KeyFormatCNDDescription

MAC

an64

M
Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here:

Key

Format

CND

Description

Beschreibung

PayTypea..11O

Defines type of Instanea payment:

ValueMeaning
sepaInstant

Instanea type "sepaInstant" is used

default, if not specified

Definiert die Art der Instanea Zahlung:

WertBedeutung
sepaInstanea type "sepa
sepaInstant

Instanea type "sepaInstant" (default)

OrderDesc

ans..768 (warning)



O

Description of purchased goods, unit prices etc.


Please note: The first 27 characters appear on the customer-account statement. You can view the full data in Axepta BackOffice.




The data sent in this parameter will be forwarded to your customer banks and some restrictions can be setup by banks on the size of this field.


Additional rule : The characters accepted are: A..Za..z0..9 / - ? : ( ) . , + BUT Diactrics such as äöüÄÖÜ, áéíóú, àèìòù, âêîôu, ... are not accepted


We strongly recommend to use the following format for the data sent in this parameter : ans..50. 



This field is the 'remittance information'

Beschreibung der gekauften Waren, Einzelpreise etc.

Bitte beachten Sie: Die ersten 27 Zeichen erscheinen auf dem Kontoauszug des Kunden. In The page DE:Wording was not found  -- Please check/update the page name used in the MultiExcerpt-Include macro können Sie die kompletten Daten einsehen.

KeyFormatCNDDescription
UserData

ans..1024

O

If specified at request,  forwards the parameter with the payment result to the shop.

KeyFormatCNDDescription
URLSuccess

ans..256

M

Complete URL which calls up  if payment has been successful. The URL may be called up only via port 443. This URL may not contain parameters: In order to exchange values between  and shop, please use the parameter UserData.

(info) Common notes:

  • We recommend to use parameter "response=encrypted" to get an encrypted response by
  • However, fraudster may just copy the encrypted DATA-element which are sent to URLFailure and send the DATA to URLSuccess. Therefore ensure to check the "code"-value which indicates success/failure of the action. Only a result of "code=00000000" should be considered successful.

KeyFormatCNDDescription
URLFailure

ans..256

M

Complete URL which calls up  if payment has been unsuccessful. The URL may be called up only via port 443. This URL may not contain parameters: In order to exchange values between  and shop, please use the parameter UserData.

(info) Common notes:

  • We recommend to use parameter "response=encrypted" to get an encrypted response by
  • However, fraudster may just copy the encrypted DATA-element which are sent to URLFailure and send the DATA to URLSuccess/URLNotify. Therefore ensure to check the "code"-value which indicates success/failure of the action. Only a result of "code=00000000" should be considered successful.

KeyFormatCNDDescription
Response

a7

O

Status response sent by  to URLSuccess and URLFailure, should be encrypted. For this purpose, transmit Response=encrypt parameter.

KeyFormatCNDDescription
URLNotify

ans..256

M

Complete URL which  calls up in order to notify the shop about the payment result. The URL may be called up only via port 443. It may not contain parameters: Use the UserData parameter instead.

(info) Common notes:

  • We recommend to use parameter "response=encrypted" to get an encrypted response by
  • However, fraudster may just copy the encrypted DATA-element which are sent to URLFailure and send the DATA to URLSuccess/URLNotify. Therefore ensure to check the "code"-value which indicates success/failure of the action. Only a result of "code=00000000" should be considered successful.

KeyFormatCNDDescription
ReqId

ans..32

O

To avoid double payments / actions, enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction / action is submitted again with the same ReqID, will not carry out the payment or new action, but will just return the status of the original transaction / action. Please note that the must have a finalized transaction status for the first initial action. Submissions with identical ReqID for an open status will be processed regularly.

KeyFormatCNDDescription
Plain

ans..50

O

A single value to be set by the merchant to return some information unencrypted in response/notify, e.g. the MID. 

"Plain"-parameter is part of encrypted "Data" in and therefore protected against manipulation. 

KeyFormatCND

Description

Custom

ans..1024

O

"Custom"-parameter is added to the request data before encryption and is part of encrypted "Data" in  request. By this they are protected against manipulation by a consumer. 

The Custom-value is added to the  response in plain text and the "|" is replaced by a "&". By this you can put a single value into Custom-parameter and get multiple key-value-pairs back in response for your own purpose. 

Please find a samples here: Custom

 


Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...

KeyFormatCNDDescription

MID

ans..30

M

MerchantID, assigned by

KeyFormatCNDDescription
PayID

an32

M

ID assigned by for the payment, e.g. for referencing in batch files as well as for capture or credit request.

KeyFormatCNDDescription
XID

an32

M

ID for all single transactions (authorisation, capture, credit note) for one payment assigned by

KeyFormatCNDDescription
TransID

ans..64

MTransactionID provided by you which should be unique for each payment

Key

Format

CND

Description

Beschreibung

Status

a..50

M

OK (URLSuccess) or FAILED (URLFailure)

AUTHORIZE_REQUEST (URLSuccess) 


Please note that you can receive a  Status = 'authorize" (Response code = 00000000) and Description=PENDING.

It may take up to an hour to get final status (depending on the bank)

OK (URLSuccess) oder FAILED (URLFailure)

AUTHORIZE_REQUEST (URLSuccess), Description=PENDING: es dauert bis zu einer Stunde bis zum finalen Status

KeyFormatCNDDescription
Description

ans..1024

M
Further details in the event that payment is rejected. Please do not use the Description but the Code parameter for the transaction status analysis!

KeyFormatCNDDescription
Code

n8

M

Error code according to  Response Codes (A4 Response codes)

Key

Format

CND

Description

Beschreibung

RefNr

ans..30

M

Reference is mandatory and must be unique for each payment, allowed characters: A..Za..z. Digits are not allowed!

Die Referenznummer des Zahlungsvorganges. Sie muss eindeutig und einmalig sein und darf nur aus folgenden Zeichen bestehen: A..Za..z. Ziffern sind nicht erlaubt!
TransactionIDans..64MUnique transaction id returned by Instanea (transfer-id).Eindeutige TransaktionsId von Instanea (transfer-id).

KeyFormatCNDDescription
UserData

ans..1024

O

If specified at request,  forwards the parameter with the payment result to the shop.

KeyFormatCNDDescription

MAC

an64

M
Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here:

KeyFormatCNDDescription
Plain

ans..50

O

A single value to be set by the merchant to return some information unencrypted in response/notify, e.g. the MID. 

"Plain"-parameter is part of encrypted "Data" in and therefore protected against manipulation. 

KeyFormatCND

Description

Custom

ans..1024

O

"Custom"-parameter is added to the request data before encryption and is part of encrypted "Data" in  request. By this they are protected against manipulation by a consumer. 

The Custom-value is added to the  response in plain text and the "|" is replaced by a "&". By this you can put a single value into Custom-parameter and get multiple key-value-pairs back in response for your own purpose. 

Please find a samples here: Custom