Skip to content

Logo

Genome

The operating system for your financial life

Supports in this guide: Payments

Provider website: genome.eu


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

  1. Get your credentials (from Genome)
  2. Whitelist Corefy's callback URL
  3. Connect in Dashboard
  4. Send an API request

Prerequisites: get from Genome

Send a request on the website or call the hotline to verify your identity and start the merchant registration process. Genome's integration team will issue the following credentials.

  • Merchant account -> Corefy field merchant_account.
  • Merchant password -> Corefy field merchant_password.
  • Signature key -> Corefy field signature_key.
  • API URL -> Corefy field api_url -> choose old (gateway.genome.eu) or new (api.genome.eu) as instructed by your Genome manager.

Important

In your Genome Dashboard, go to Account settings -> Firewall, click Send new request, and submit both Corefy's own IP list from the integration docs and the callback URL https://psp-ext.paycore.io/genome/callback for whitelisting.

EUR, USD, GBP, CAD, AUD, UAH.


Payments processing (connect H2H Merchant account, create payment-invoice)

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

Open Genome in the provider directory and press Connect at Genome Provider Overview page in the New connection section.

Step 2 - Fill in fields and select settings

  • Merchant account
  • Merchant password
  • Signature key
  • API URL
  • Currency / Features -> choose values available for your account
  • Test Mode -> (enable if you are using sandbox credentials)

Success

You have connected Genome H2H Merchant account!


First request to Corefy API (MIN)

What it does: creates a payment-invoice; card data itself is collected and submitted separately by Corefy's checkout/SDK layer, not as part of this request. Genome may return a 3D Secure challenge redirect depending on the card.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "3c4d5e6f-7a8b-4c9d-8e02-3f4a5b6c7d8e",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "email": "test@example.com"
      }
    }
  }
}

Important

customer.email is required - the payment is rejected before it's sent to Genome if it's missing.

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "4d5e6f7a-8b9c-4d0e-8f13-4a5b6c7d8e9f",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "email": "test@example.com",
        "address": {
          "country": "DE"
        },
        "metadata": {
          "country": "DE",
          "ip": "203.0.113.10"
        }
      }
    }
  }
}

Important

  • first_name/last_name sent to Genome are derived from the card's own embossed cardholder name, not from a customer.name field.
  • The country sent to Genome is resolved in order: customer.address.country, then customer.metadata.country, then your customer's auto-detected IP country; the user IP follows the same pattern via customer.metadata.ip.
  • No Options or Constants are configured for this connector.

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


Refunds

Genome supports partial refunds, but only one refund per payment (no multiple partial refunds against the same payment).


Additional info

  1. Active reconciliation is available - both the asynchronous callback and an active status request can finalize the payment.
  2. No recurring - this connector does not support saving/charging a token through Corefy.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify the merchant account, password, and signature key for the selected API URL and environment (test_mode)
  • Callbacks not arriving -> confirm Corefy's IPs and the callback URL are whitelisted in Genome's Firewall settings
  • Payment rejected immediately -> confirm customer.email is present in the request
  • Currency or service is not supported -> confirm allowed currencies/features in your Genome account and in Corefy
  • Refund fails with multiple attempts -> only one refund per payment is allowed

Question

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