Top-up by card-related payments

To start using ConnectPay’s card-related top-up to your customer’s accounts, follow these steps:

1. Initiate a card top-up payment API request to baas/merchant/topup/ following the example below from our API reference: Initiate Card Top up API
2. redirectUrl in Initiate Card Top up API should be whitelisted in your devApp in callbackUrls.
3. Use your customer’s IBAN account number in accountNumber.
4. 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 Issuer. Save paymentId for further status check. Response example below:

{
  "merchant": {
    "generic1": "0bf1e34e",
    "generic2": "0bf1e34e",
    "generic3": "0bf1e34e"
  },
  "payment": {
    "paymentId": "8c36b04b-fd6e-4442-b837-a3dcafcfc5ff",
    "redirectUrl": "https://pay.connectpay.com?key=8c36b04b-fd6e-4442-b837-a3dcafcfc5ff"
  }
}

{
  "merchant": {
    "generic1": "0bf1e34e",
    "generic2": "0bf1e34e",
    "generic3": "0bf1e34e"
  },
  "payment": {
    "paymentId": "8c36b04b-fd6e-4442-b837-a3dcafcfc5ff",
    "redirectUrl": "https://pay.connectpay.com?key=8c36b04b-fd6e-4442-b837-a3dcafcfc5ff"
  }
}

3. After your consumer is done with payment journey (authorizes a payment at Issuer), we will redirect 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 Card Top up API request. All transactions require 3DS authorization. Exemptions might be applied by the Consumer’s Issuer or Digital Wallet operators.
4. Sometimes, card schemes or Issuer 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, you can use such card numbers (CVV -any 3 digits, card expiry – future date):

1. 4242424242424242 – Visa, credit card, success response, 3DS challenge enabled
2. 5436031030606378 – MasterCard, credit card, success response, 3DS challenge enabled
3. 4485040371536584 – Visa, credit card, success response, 3DS frictionless response
4. 4544249167673670 – Visa, credit card, failure response, Insufficient funds
5. 4539253655711767 – Visa, credit card, failure response, Stolen card
6. If you send us amount 99.99 EUR, it will return status PendingProvider, meaning it got stopped for manual review. In non-prod environment such transactions are not approved, unless you contact us.
7. When testing Apple Pay requests, follow the process defined here Sandbox Testing – Apple Pay – Apple Developer
8. When testing Google Pay requests, follow the process for mocked cards here.

You can see full sequence diagram below:

• When sending the accountNumber., make sure it’s active and belongs to the consumer you’ve onboarded;
• If success response received from Issuer / Card schemes, top up transactions are settled instantly to consumer’s IBAN account. For manually stopped transactions a review will be performed before settlement.
• ConnectPay does not charge any fees from your consumer during this flow.

Limits

Limits are applied for card transactions (per end-user):

1. MIN transaction amount 10 EUR
2. MAX transaction amount 10 000 EUR
3. Daily limit 10 000 EUR
4. Monthly limit 500 000 EUR

Smaller limits might be applied by Issuer or Digital Wallets.

Card Scheme Field Validation Requirements

Card schemes set strict data-quality rules for the sender and recipient details on Top up Transactions, which power account top-ups. If a top-up carries details that break these rules, the card scheme or issuer declines the payment.

These rules are not enforced by our API. Our API accepts top-up requests regardless of whether these fields meet card scheme requirements. Validation happens downstream, during card scheme processing, so a request that passes our API can still be declined later.

To avoid unnecessary declines, validate your customer data that is provided to us during onboarding in your own integration before sending a top-up request. The sections below list the requirements per field.

Customer names

Address lines

City and country