Skip to content

Logo

PayPugs

Supports in this guide: Payments

Provider website: paypugs.com

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

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

Choose account type

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

  • If you do card payments -> choose H2H Merchant account

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

Prerequisites: get from PayPugs

Get the following values for your PayPugs project/account:

  • API Key -> Corefy field api_key -> where to find: PayPugs backoffice / issued by PayPugs manager
  • Brand ID -> Corefy field brand_id -> where to find: PayPugs backoffice / issued by PayPugs manager
  • S2S Token -> Corefy field s2s_token -> only needed if you'll use the server to server API Type
  • Webhook Public Key -> Corefy field webhook_public_key -> optional — if left blank, Corefy automatically registers a webhook with PayPugs and retrieves this key for you when the connection is saved
Payments processing (connect H2H Merchant account, create payment-invoice)

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

Open PayPugs in the provider directory and press Connect at PayPugs Provider Overview page in the New connection section. Choose H2H Merchant account.

Step 2 - Fill in fields and select settings

  • API Key
  • API Type -> server to server (card data submitted directly by Corefy) or direct post (customer completes payment on PayPugs' own hosted page)
  • S2S Token -> (only relevant for the server to server API Type)
  • Brand ID
  • Webhook Public Key -> (optional — auto-provisioned if left blank)

Choose Currency and Features. You can set these parameters according to available currencies and features for your PayPugs account, but it is necessary to check details of the connection with your Corefy account manager.

Success

You have connected PayPugs H2H Merchant account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice.

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 100,
      "customer": {
        "reference_id": "55041b5b-adfd-4073-a92b-fd8b495a4cc1",
        "email": "johnsmith@gmail.com"
      },
      "reference_id": "86e68af6-6b95-4cc0-be16-e4df8044604c"
    }
  }
}

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 100,
      "customer": {
        "reference_id": "bc75bc54-5023-4f98-8c0d-ec5ed7e8f380",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "individual_tax_id": "123456789",
        "address": {
          "country": "DE",
          "region": "Berlin",
          "city": "Berlin",
          "post_code": "10115",
          "full_address": "1st Street 1"
        }
      },
      "reference_id": "08f5e97c-1170-4bda-9625-3bde3c6dcd20"
    }
  }
}
All fields above are always forwarded as-is when present — there's no option to suppress them.

Extended request (MAX)

Why add extra fields (typical reasons): - Provide additional customer details for compliance/reconciliation - Positively influence conversion rate - Include optional fields required by your specific flow

Options

Options are configured on the Corefy side and affect how Corefy builds provider requests or processes responses.

Currently available options (1)

  • custom_finalization_with_delay - delays finalizing certain 3DS/authorization failures, rechecking the status again before giving up
custom_finalization_with_delay

What it does: when PayPugs returns a response that looks like a transient 3DS-authentication or authorization failure (an overdue/error/released status paired with a 3DS or authorization failure code), Corefy waits the number of seconds you set here, then re-checks the transaction's status instead of immediately finalizing it as failed.

When to use: enable it if you're seeing transactions finalized as failed that later turn out to have succeeded on PayPugs' side shortly after.

Default: not set (no delay/recheck — the response is used as-is)

Allowed values: an integer number of seconds (1-2 digits)

Additional info

  1. Callback routing uses a dedicated, fixed endpoint that Corefy manages on your behalf — you don't need to configure anything in your PayPugs account for it. Signature validation is applied using your Webhook Public Key.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify credentials for the selected environment and account type
  • Currency or service is not supported -> confirm allowed currencies/features in your PayPugs account and in Corefy
  • Not sure which account type to use? -> ask your Corefy account manager
  • Connection fails at setup -> if you left Webhook Public Key blank, Corefy attempts to auto-register a webhook with PayPugs during connection — confirm your API Key/Brand ID are correct if this fails

Question

Still looking for help connecting your PayPugs account? Please contact our support team!