Top-up user’s account

If you are a Platform/Marketplace (Baas API user), your customers can use ConnectPay’s merchant services to top-up their IBAN accounts. The purpose of top-up is to collect non-commercial transactions to your customers’ accounts.

Stage:

To start testing this service, drop a message to [email protected] mentioning you will want to integrate Top-up APIs. By default, this service is disabled for merchants.

Production:

To receive this service, you will need to have BaaS contract – just inform your account manager about it, as top up is disabled by default.

To start using ConnectPay’s Payment initiation service to top-up your customer’s accounts, follow these steps:

  1. Initiate a top-up payment API request to baas-sca/merchant/partner/topup/pis following example below from our API reference: Initiate top-up by PIS API
  2. If the request was successful, you will receive a response with HTTP code 201 and paymentId and redirectUrl in the response body. You have to redirect your customer to redirectUrl to authorize a payment within their provider (bank). Save paymentId for further status check. Response example below:
{
  "merchant": {
  },
  "payment": {
    "paymentId": "5e864dad-4f10-4b91-bf3f-b8d0c9819d3a",
    "redirectUrl": "https://pay-stage.connectpay.com?key=8c36b04b-fd6e-4442-b837-a3dcafcfc5ff"
  },

  1. After your consumer is done with the payment journey (authorizes payment in their bank environment), the bank will redirect the consumer to our result page (Failed, In progress or Success), from which we have auto-redirection to your environment. We redirect consumers to your redirectUrl provided in Initiate top-up API request.
  2. Sometimes, provider may not respond immediately with the final payment status information. In such cases, we will periodically check at Provider for final status and update payment information. Same way, you should periodically check payment status using Get payment details API . Or you can subscribe to our payment status notification events and wait for status change notification.

For testing only. When testing requests in the stage environment, please note that not all providers support frontend. We recommend selecting these details while testing:

1. For DE country and PIS method – Fake Bank with Client Keys (enter it in search), provider ID c3e4f215-dde4-4d0c-9a48-bc7274c90977 . Test credentials:
User: username
Password: secret
Confirmation code: 123456
2. For LT country and PIS method – Siauliu bankas, provider ID a7640cb7-4dec-4a44-a9ad-b918c803254e
3. For CARD payment method, use card No 4242424242424242 for success result and No 4539467987109256 for failed result.

Or you can subscribe to our payment status notification events and wait for the status change notification.

You can see the full sequence diagram below:

After authorization within their bank or issuer, the Consumer will be redirected back to the widget and will be presented with payment status information. All commercial transactions require SCA for payments or 3DS authorization for card-related payments. Exemptions might be applied by the Consumer’s bank or Issuer.

As a final step of the payment journey, by pressing the Return to Merchant button, the Consumer will be redirected back to your website using the web address provided via redirectUrl parameter in the Initiate top-up API request.

  • When sending a creditor account, make sure it’s active and belongs to the consumer you’ve onboarded;
  • Delivery of a payment might be different (not all providers support SEPA INST), please check providers and schemes they support here.

Authentication

Accounts

Payment details

Notifications

Scroll to Top