Skip to content

One Payment

One Payment

Supports in this guide: Payments

Provider website: 1payment.com

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

  1. Get your credentials (from One Payment)
  2. Connect in Dashboard
  3. Send an API request

Prerequisites: get from One Payment

Contact your One Payment account manager to get your account verified and receive the following credentials.

  • Partner ID -> Corefy field partner_id.
  • Project ID -> Corefy field project_id.
  • Secret key -> Corefy field secret_key.

Card payments only.

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

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • Partner ID
  • Project ID
  • Secret key
  • Currency -> a single currency, matched against the currency configured on your One Payment project

Success

You have connected One Payment 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.

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6be05631-8710-4b14-a369-1928a2b70eda",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10
    }
  }
}

Important

  • customer is not used by this connector at all - no customer field is ever sent to One Payment.
  • The cardholder name sent to One Payment comes from the card's own embossed name; if that's missing, customer.name is used instead; if both are missing, a fixed placeholder name ("John Doe") is sent rather than leaving the field empty.
  • The merchant website URL sent to One Payment is sourced from your own Corefy merchant profile; if that isn't set, a fixed placeholder URL is sent instead.
  • If your account's 3D Secure mode is set to strictly require 3DS, or to skip 3DS entirely, the payment is auto-declined before being sent to One Payment (status: unable to determine 3DS enrollment) - leave the 3DS mode on automatic determination for this connector to work.

Payment - MAX

This connector has no optional customer or extended fields - the MIN example above is also the MAX request.

Refunds

One Payment supports refunds for the full amount only - no partial refunds, and only one refund per 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.
  3. No Options or Constants are configured for this connector.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify the Partner ID, Project ID, and secret key
  • Payment auto-declined with "unable to determine 3DS enrollment" -> set your account's 3DS mode to automatic rather than "always require" or "always skip"
  • Currency mismatch error -> the connected currency must match the currency configured on your One Payment project
  • Refund fails with multiple attempts -> only one, full-amount refund per payment is allowed

Question

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