Skip to content

Logo

Rastpay

Supports in this guide: Payments

Provider website: rastpay.com

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

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

Choose account type

Rastpay 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 Rastpay

Get the following values for your Rastpay project/account:

  • API Key -> Corefy field api_key -> where to find: Rastpay backoffice / issued by Rastpay manager
  • Signing Key -> Corefy field signing_key -> where to find: Rastpay backoffice / issued by Rastpay manager, used to verify callback signatures
Payments processing (connect H2H Merchant account, create payment-invoice)

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • API Key
  • Signing Key
  • Test Mode -> (enable if you are using sandbox credentials)

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

Success

You have connected Rastpay 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,
      "reference_id": "86e68af6-6b95-4cc0-be16-e4df8044604c"
    }
  }
}
customer is entirely optional for this flow — Rastpay auto-generates a reference ID if customer.reference_id is absent, and customer.email is simply omitted from the outbound request if not provided.

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",
        "address": {
          "country": "DE",
          "city": "Berlin",
          "post_code": "10115",
          "full_address": "1st Street 1"
        }
      },
      "reference_id": "08f5e97c-1170-4bda-9625-3bde3c6dcd20"
    }
  }
}
Unlike most providers on this platform, Rastpay has no send_customer_data-style option: whatever billing details are present in customer (name, email, phone, address) are always forwarded as-is. Confirm the currencies available for your account with your Corefy account manager — Rastpay doesn't have a fixed currency list on the Corefy side.

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

Constants (fallback fields)

Constants are static values that Corefy can send to the provider instead of dynamic data from your API request, when those fields are missing in the request.

Priority (predictable rule): 1. If a value is present in the request -> Corefy uses the request value 2. Else if the constant is set -> Corefy uses the constant 3. Else -> provider may reject the request or apply its defaults (depends on provider)

Currently available constants (constant -> Corefy API field)

  • FIRST_NAME -> customer.name
  • LAST_NAME -> customer.name
  • EMAIL -> customer.email
  • PHONE -> customer.phone
  • FULL_ADDRESS -> customer.address.full_address
  • CITY -> customer.address.city
  • COUNTRY -> customer.address.country
  • POST_CODE -> customer.address.post_code

Additional info

  1. Callback routing is handled automatically (Corefy generates the callback URL per transaction) — signature validation is applied.

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 Rastpay account and in Corefy
  • Missing customer data fields -> set constants (see "Constants") or provide fields in the API request
  • Not sure which account type to use? -> ask your Corefy account manager

Question

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