Skip to end of metadata
Go to start of metadata

URL for "faulty payment"

Format

CHAR(2..255)

Scheme

<scheme>://<host>/<path>
<scheme>://<host>/<path>?<query>

scheme-pattern: [a-zA-Z]{1}[a-zA-Z0-9]{1,9}

URL is required for any type of redirect payments, e.g.

  • Bancontact, EPS, Giropay, iDEAL, Multibanco, PostFinance, Przelewy24, SOFORT, Trustly, ...
  • PayPal, Paydirekt, Paysafecard, ...
  • credit card with 3-D secure

Allowed schemes for URL:

  • For Channel "Frontend" / "Client-API" only schemes "http" or "https" allowed.
  • For Channel "Server-API" individual schemes like "app://app.domain.com" is allowed

URL can be

  • either defined in PMI -> configuration -> portal
    -> then this URL is used as default
    (this requires channel "Frontend" to be avalibale)
  • or it can be specified via API parameter
    -> then this URL overrides the PMI-configuration.
Example 
Valid for all channels (Server, Client, Frontend): 
https://www.domain.com/success.html
https://www.domain.com/success.html?exit=success&txid=__txid__
https://www.domain.com/back.html?exit=back
https://www.domain.com/error.html?exit=error&errorcode=__errorcode__

Valid additionally for Server-API:
app://app.domain.com/success.html?exit=success&txid=__txid__
myscheme://myapp.domain.com/success.html?exit=success&txid=__txid__
myscheme://myapp.domain.com/error.html?exit=error&errorcode=__errorcode__


Payment specific:

Payment type

Comment

Redirect payment

For redirect payments (e.g. PayPal, Giropay, SOFORT, ...) an URL has to be provided.
It can be

  • either defined in PMI -> configuration -> portal
    -> then this URL is used as default
  • or it can be specified via API parameter
    -> then this URL overrides the PMI-configuration.
  • No labels