Mobilum (GDPaytech)

Supports in this guide: Payments

Provider website: gdpaytech.pl

What you need to do for start processing transactions (brief summary)

1. Choose account type
2. Get your credentials (from Mobilum (GDPaytech))
3. Connect in Dashboard
4. Send an API request

Choose account type

Mobilum (GDPaytech) can be connected in different ways (depending on your needs):

• If you do BLIK payments (the customer enters a BLIK code on the Corefy hosted payment page) -> choose Provider account

If you are not sure which one to use, confirm with your Corefy account manager.

Prerequisites: get from Mobilum (GDPaytech)

Get the following values for your Mobilum (GDPaytech) project/account:

• API Key -> Corefy field api_key -> example: a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6 -> used to authorize every request to the Mobilum (GDPaytech) API -> where to find: Mobilum (GDPaytech) backoffice / issued by Mobilum (GDPaytech) manager
• API URL (optional) -> Corefy field api_url -> example: https://payments.gdpaytech.pl -> base URL of the Mobilum (GDPaytech) API. If left empty, the test environment https://payments-test.gdpaytech.pl is used, so set it for production -> where to find: Mobilum (GDPaytech) backoffice / issued by Mobilum (GDPaytech) manager
• Webhook API Key (optional in the form, required to accept webhooks) -> Corefy field webhook_api_key -> example: f6e5d4c3b2a1f6e5d4c3b2a1f6e5d4c3 -> used to validate the Api-Key header of incoming webhooks -> where to find: Mobilum (GDPaytech) backoffice (Settings -> Webhook configuration) / issued by Mobilum (GDPaytech) manager

The API Key and the Webhook API Key are issued separately for the test and production environments.

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8d2f6a41-3c7e-4b9d-a5e0-7f1c2b3d4e5f",
      "service": "blik_pln_invoice",
      "currency": "PLN",
      "amount": 100
    }
  }
}

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "c4e1b7a9-6d2f-4a3e-8b5c-9e0f1a2b3c4d",
      "service": "blik_pln_invoice",
      "currency": "PLN",
      "amount": 100,
      "customer": {
        "reference_id": "5b3a9c1e-2f4d-4e8a-9b7c-1d2e3f4a5b6c",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+48500100200",
        "metadata": {
          "ip": "203.0.113.10",
          "client_agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64)"
        }
      }
    }
  }
}

Additional info

1. Webhooks are required. Without them Mobilum (GDPaytech) doesn't deliver payment results to Corefy, and payments are finalized only by status checks. In the Mobilum (GDPaytech) backoffice, go to Settings -> Webhook configuration and set it up separately for the test and production environments:

   • Webhook URL -> the Corefy callback endpoint /gdpaytech/callback. Mobilum (GDPaytech) adds the event path itself, so webhooks arrive at /gdpaytech/callback/paymentFinished.
   • API key -> the same value you entered in the Webhook API Key (webhook_api_key) field of the connection. Webhooks with a missing or different key are rejected.

2. Mobilum (GDPaytech) sends webhooks only for successful and failed payments. Cancellations have no webhook, so Corefy gets them from status checks.

3. A BLIK code is valid for a short time and must be confirmed by the customer in their banking app. If the customer never enters the code, use the finalize_unconfirmed_after_minutes option to close such payments.

FAQ / Troubleshooting

• Invalid credentials / auth error -> verify you used the API Key for the chosen environment, and that API URL points to the matching environment (empty = test environment)
• Payments stay in processing -> check the webhook configuration in the Mobilum (GDPaytech) backoffice and that its API key matches Webhook API Key in the connection; consider setting finalize_after_minutes / finalize_unconfirmed_after_minutes
• Payment declined with invalid request -> make sure the payer's IP address and User-Agent are available: pass them in customer.metadata, or set the user_ip / user_agent constants
• Payment declined with limit violation -> the amount is outside the transaction limits set for your Mobilum (GDPaytech) account (for example, below the minimal single transaction amount); check the limits with your Mobilum (GDPaytech) manager
• Payment declined with invalid details -> the customer entered a wrong or already used BLIK code; ask them to generate a new code and pay again
• Not sure which account type to use? -> ask your Corefy account manager