Skip to content

Logo

Advanced Payment Solutions (APS)

We handle the payments. You handle the business.

Supports in this guide: Payments, Payouts

Provider website: aps.money

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

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

Choose account type

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

  • If you do H2H card payments (card data sent directly) -> choose H2H Merchant account
  • If you do hosted-page payments (customer redirected to a checkout page) -> choose Merchant account
  • If you do payouts -> choose Provider account

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

Prerequisites: get from APS

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

For H2H Merchant account:

APS has two API generations for this flow - API Version 3 (current, simpler REST credentials) and API Version 1 (legacy, built on the Stellar network). Your account manager will tell you which one applies to you.

  • Use API Version 3 -> Corefy field use_api_version_3 -> enable for API Version 3, leave disabled for the legacy Stellar-based flow.
  • Deposit Method -> Corefy field deposit_method -> the specific payment rail configured for your account with APS.
  • Callback Secret Key -> Corefy field callback_secret_key.

If using API Version 3:

  • Merchant GUID -> Corefy field merchant_guid.
  • App Token -> Corefy field app_token.
  • App Secret -> Corefy field app_secret.

If using the legacy API Version 1 (Stellar-based):

  • Merchant Stellar Address -> Corefy field merchant_stellar_address.
  • Stellar Seed -> Corefy field stellar_seed -> this is the private signing key for your Stellar account; handle it with the same care as any other secret credential.
  • Web Auth URL -> Corefy field web_auth_url.
  • KYC Server URL -> Corefy field kyc_server_url.
  • Direct Payment URL -> Corefy field direct_payment_url.
  • Asset Code / Asset Issuer -> Corefy fields asset_code/asset_issuer -> the Stellar asset your account settles in.

For Merchant account:

  • Merchant GUID -> Corefy field merchant_guid.
  • App Token -> Corefy field app_token.
  • App Secret -> Corefy field app_secret.
  • Method GUID (optional) -> Corefy field method_guid -> identifies the specific payment method (card, Apple Pay, etc.) configured with APS for this connection.
  • Callback Secret Key (optional) -> Corefy field callback_secret_key.

For Provider account:

  • Merchant GUID -> Corefy field merchant_guid.
  • App Token -> Corefy field app_token.
  • App Secret -> Corefy field app_secret.
  • Currency -> Corefy field currency -> single-select, USD or EUR.
  • Method ID (optional) -> Corefy field method_id -> the payout rail configured with APS for this connection.
  • Callback Secret Key (optional) -> Corefy field callback_secret_key.
Payments processing (connect H2H Merchant account, create payment-invoice)

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

Open Advanced Payment Solutions (APS) in the provider directory and press Connect at Provider Overview page in the New connection section. Choose H2H Merchant account.

Step 2 - Fill in fields and select settings

Fill in the fields for whichever API Version your account manager confirms (see Prerequisites above), plus:

  • Deposit Method
  • Callback Secret Key
  • Test Mode -> (enable if you are using sandbox credentials)

Choose Currency / Features; available currencies depend entirely on how your account is set up with APS - check with your Corefy account manager.

Success

You have connected Advanced Payment Solutions (APS) 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. APS may return a 3D Secure redirect depending on the card.

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",
        "address": {
          "country": "FR",
          "street": "1 Main street",
          "city": "Paris",
          "post_code": "75000"
        }
      }
    }
  }
}

customer is entirely optional - anything you don't send falls back to the Constants below, or is simply left blank on APS's 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)

  • EMAIL -> customer.email
  • COUNTRY -> customer.address.country
  • STREET -> customer.address.street
  • CITY -> customer.address.city
  • POST_CODE -> customer.address.post_code

No Options are configured for this connector.

Refunds

This connector supports partial and multiple refunds against the same payment.

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

Connect Merchant account in Corefy Dashboard

Step 1 - Open connection form

Open Advanced Payment Solutions (APS) in the provider directory and press Connect at Provider Overview page in the New connection section. Choose Merchant account.

Step 2 - Fill in fields and select settings

  • Merchant GUID
  • App Token
  • App Secret
  • Method GUID (optional)
  • Callback Secret Key (optional)
  • Test Mode -> (enable if you are using sandbox credentials)

Important

This connection is locked to a single payment method (whatever Method GUID points to in your APS setup) - connect a separate Merchant account for each method/currency combination you need.

Success

You have connected Advanced Payment Solutions (APS) Merchant account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice and redirects the customer to APS's hosted checkout page for whichever method this connection is configured for.

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

This connector also exposes Apple Pay as its own service code (applepay_eur_hpp) when the connection's Method GUID is set up for it - the request shape is otherwise identical.

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",
        "address": {
          "country": "FR",
          "street": "1 Main street",
          "city": "Paris",
          "post_code": "75000"
        }
      }
    }
  }
}

customer is entirely optional - anything you don't send falls back to the Constants below.

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 are configured for this flow.

Constants (fallback fields)

Configured specifically for the applepay_eur_hpp service.

Currently available constants (constant -> Corefy API field)

  • CUSTOMER_EMAIL -> customer.email
  • CUSTOMER_FIRST_NAME -> customer.name (first part)
  • CUSTOMER_LAST_NAME -> customer.name (second part)
  • CUSTOMER_COUNTRY -> customer.address.country
  • CUSTOMER_STREET -> customer.address.street
  • CUSTOMER_CITY -> customer.address.city
  • CUSTOMER_POST_CODE -> customer.address.post_code
  • CUSTOMER_IP -> customer's IP address
Payouts processing (connect Provider account, create payout-invoice)

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

Open Advanced Payment Solutions (APS) in the provider directory and press Connect at Provider Overview page in the New connection section. Choose Provider account.

Step 2 - Fill in fields and select settings

  • Merchant GUID
  • App Token
  • App Secret
  • Currency -> USD or EUR
  • Method ID (optional)
  • Callback Secret Key (optional)
  • Test Mode -> (enable if you are using sandbox credentials)

Success

You have connected Advanced Payment Solutions (APS) Provider account!

First request to Corefy API (MIN)

What it does: creates a payout-invoice and sends funds directly to a card.

Payout - MIN

POST /api/payout-invoices 

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

Important

fields.card_number is required. This connector also supports card payouts in USD (use payment_card_usd as the service code).

Payout - MAX

POST /api/payout-invoices 

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "3c6d2f8e-8a2a-4e7a-9b1a-2f6a7b9c0d1e",
      "service": "payment_card_eur",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "address": {
          "country": "FR",
          "street": "1 Main street",
          "city": "Paris",
          "post_code": "75000"
        }
      },
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

customer is entirely optional - name is split into first/last for the beneficiary; email/address, when sent, are only forwarded as recipient details.

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 are configured for this flow.

Additional info

  1. Callback routing is automatic - Corefy generates the callback URL per transaction and sends it to APS as part of the request itself; nothing to configure in APS's own back-office.

  2. This connector exposes Apple Pay as its own service code on the Merchant account flow (applepay_eur_hpp) - see the note under that flow's Payments section above.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify the credentials for the account type and API Version you're using - H2H Merchant account has two distinct credential sets depending on Use API Version 3
  • Sale rejected or stuck pending -> confirm the Deposit Method / Method GUID / Method ID matches a method actually configured for your account with APS
  • Currency or service is not supported -> confirm allowed currencies/methods in your APS account and in Corefy

Question

Still looking for help connecting your Advanced Payment Solutions (APS) account? Please contact our support team!