Monetix

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Project ID
• Secret Key
• Trusted (optional)
• Test Mode -> (enable if you are using sandbox credentials)

Choose Currency and Features. EUR is confirmed; check with your Corefy account manager which are enabled for your 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": "8e3dbbb0-17af-4c9a-bedb-93bdac6900a2",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "address": {
          "country": "DE",
          "city": "Berlin",
          "street": "1 Main street",
          "post_code": "10115"
        }
      }
    }
  }
}

customer is entirely optional - anything you don't send falls back to the Constants below (or is simply omitted) instead of failing the request. customer.phone is only actually required when the card's issuing country is QA or BR (detected automatically from the card BIN). CVV is optional on this connector - if your checkout flow doesn't collect it, the sale still goes through without it.

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 (4)

• ignore_callback - tells Corefy to disregard Monetix's own callback notifications entirely.
• async_acs_data_extraction - actively polls for 3D Secure (ACS) challenge data instead of waiting once for the callback.
• enable_visa_aft_refund_rules - skips the normal 24-hour refund delay for Visa cards.
• enable_mastercard_aft_refund_rules - skips the normal 24-hour refund delay for Mastercard cards.

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)

• CUSTOMER_NAME -> customer.name
• CUSTOMER_EMAIL -> customer.email
• PHONE -> customer.phone
• COUNTRY -> customer.address.country
• CITY -> customer.address.city
• STREET -> customer.address.street
• ZIP -> customer.address.post_code
• FULL_ADDRESS -> customer.address.full_address

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Project ID
• Secret Key
• Secret Key (URL)
• Healthcheck URL
• Token / Token Key (optional)
• Test Mode -> (enable if you are using sandbox credentials)

Choose Currency / Features - this is one of the broadest connectors on the platform for Southeast/South Asia - see Additional info for the full method list.

First request to Corefy API (MIN)

What it does: creates a payment-invoice and returns a redirect link to Monetix's hosted payment page for the chosen local method.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8e3dbbb0-17af-4c9a-bedb-93bdac6900a2",
      "service": "ovo_idr_hpp",
      "currency": "IDR",
      "amount": 100000
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "ovo_idr_hpp",
      "currency": "IDR",
      "amount": 100000,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "address": {
          "country": "ID",
          "city": "Jakarta"
        }
      },
      "fields": {
        "bank_code": "014"
      }
    }
  }
}

customer is entirely optional - Corefy auto-generates a customer id if you omit it. fields.bank_code is only relevant for the online-banking/bank-transfer methods that need to know which specific bank to route to.

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

No Options or Constants are configured for this flow.

Connect Provider account in Corefy Dashboard

Uses the same Provider account connection as Payments above - one connection covers both directions, there's nothing extra to fill in for payouts specifically.

First request to Corefy API (MIN)

What it does: creates a payout-invoice and sends funds to a card, a named local bank, or a mobile money account.

Payout - MIN (card)

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "0dde9e79-2c64-4703-adaf-93d710633401",
      "service": "payment_card_eur",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith"
      },
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

Payout - MIN (named bank)

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "3c6d2f8e-8a2a-4e7a-9b1a-2f6a7b9c0d1e",
      "service": "bank_central_asia_idr",
      "currency": "IDR",
      "amount": 100000,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith"
      },
      "fields": {
        "account_number": "1234567890"
      }
    }
  }
}

fields.card_number is required for card payouts; the cardholder's name is derived from customer.name. For named-bank payouts, the required field is usually fields.account_number (occasionally fields.bank_account_number depending on the bank) plus customer.name for the recipient - ask your account manager for the exact field key for your chosen bank. Mobile money methods (Pakistan, Bangladesh, Egypt) need fields.phone_number instead.

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

No Options or Constants are configured for this flow.