Initiate Pay by Bank

How does it work?

  1. Call POST v2/moneyins/paybybank/transfer/init, to receive a redirect URL and the transaction Id.

  2. Redirect the end-user to your bank selection page, were they can select their bank from the displayed list.

    Note: If you specify the bankId in the request body, the end-user will be directed to their bank.

    For further information on how to obtain bankIds, see: /v2/moneyins/ paybybank/transfer/banks
  3. Once the end-user selects their bank they are redirected to the bank webpage to enter their credentials.

Note: If you have previously specified the bankId the end-user only needs to enter their bank credentials at this stage.

  1. After successfully entering their credentials, the end-user will go through Strong Customer Authentication (SCA) to confirm their identity (SCA examples include: face recognition or mobile Bank App software). Some bank ask to SCA before entering credentials.

  2. Once successfully authenticated the end-user only needs to verify and validate the amount, comments and so forth on the bank website.

  1. After submitting the payment, the end-user will be redirected to:
  • returnUrl in case of success
  • cancelUrl in case of cancellation
  • errorUrl in case of error.

These 3 URLs must be publicly accessible for the end-user. It must also be accessible to our WebKit server to send requests to the end-user.

How does it work?

  1. Call POST /v2/moneyins/paybybank/transfer/init to receive:

    • A redirect URL
    • The transaction ID
  2. Redirect the end user to the bank-selection page, where they can select their bank from the displayed list.

    Note: If you include the bankId in the request body, the end user is redirected directly to their bank.

    To retrieve the available bank IDs, call:

    GET /v2/moneyins/paybybank/transfer/banks

  3. After selecting their bank, the end user is redirected to the bank's website or application to enter their credentials.

    Note: If the bankId was included in the initial request, the end user does not need to select their bank and can proceed directly to authentication.

  4. The end user completes Strong Customer Authentication (SCA) to confirm their identity.

    Authentication methods may include:

    • Facial recognition
    • Fingerprint recognition
    • Confirmation through the bank's mobile application
    • A one-time password

    Depending on the bank, SCA may be requested before or after the end user enters their credentials.

  5. Once authenticated, the end user reviews and confirms the payment details, including the amount and payment reference, on the bank's website or application.

  6. After the payment is submitted, the end user is redirected to one of the following URLs:

    • returnUrl if the payment is successfully submitted
    • cancelUrl if the end user cancels the payment
    • errorUrl if an error occurs

Important: The returnUrl, cancelUrl, and errorUrl must be publicly accessible to both the end user's browser and Lemonway's WebKit servers.


Body Params
string
required

returnUrl in case of success

string
required

cancelUrl in case of cancellation

string
required

errorUrl in case of error

string
required

The country code associated with the payment bank. ISO Alpha-2 codes accepted: (FR) France, (ES) Spain, (IT) Italy, (DE) Germany, and (PT) Portugal

string

If you use the bankId in the call, the end-user will be redirected to their bank. They will not have to select a bank from a list provided. To get a comprehensive list of bankIds call the GET v2/moneyins/paybybank/transfer/banks specifying the ISO Alpha-2 Country Code for example FR for France.

int32
enum

The 'TransferType' can be set to:

  • Instant: Faster SEPA instant transfer.Funds are credited within 15 minutes if supported by the payer's bank.
  • Classic: Standard SEPA credit transfer. Funds are credited in 2–3 business days.

If not provided, the default value is 'Classic'.
0 = Undefined.
1 = Instant.
2 = Classic.

Allowed:
string
length between 0 and 50

Unique ID of the call, generated by your server. This ID can be used as a search field when looking for operation details

string
required
length between 0 and 256

Payment Account ID to Credit

int32

Amount to Debit
Amounts are given as integer numbers in cents

int32

Your Fee
Amounts are given as integer numbers in cents

string
length between 0 and 140

Comment Regarding the Transaction

boolean

If true:

  1. [amountCom] will be ignored and will be replaced with Lemonway's fee
  2. You will not receive any fee
Headers
string
required

Authorization bearer (OAuth 2)

string

Response language accepted by final client (PSU). English by default

string
required

IP address of the final client (PSU).

string

User-agent of the final client (PSU).

Responses

401

Unauthorized

500

InternalServerError

Language
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json