Skip to content

Logo

Payment Asia

The Answer to One-stop eBusiness Solution. Grasp Business Opportunities in Cashless Transactions.

Supports in this guide: Payments, Payouts

Provider website: paymentasia.com

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

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

Prerequisites: get from Payment Asia

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

  • Merchant ID -> Corefy field merchant_id
  • Merchant Token -> Corefy field merchant_token
  • Secret Code -> Corefy field secret_code - used to sign every request and verify callbacks; can be updated later from the Dashboard
Payments processing (connect Provider account, create payment-invoice)

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields

  • Merchant ID
  • Merchant Token
  • Secret Code

Success

You have connected Payment Asia Provider account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice for a bank-transfer payment processed through Payment Asia's hosted payment page (HPP). Available for PHP, THB and VND.

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "5e1a5103-c972-4772-9c5d-6ee44d07cb7c",
      "service": "bank_transfer_aggregated_php_hpp",
      "currency": "PHP",
      "amount": 540,
      "service_fields": {
        "first_name": "John",
        "last_name": "Doe",
        "phone": "+0123123123",
        "email": "test@mail.com"
      }
    }
  }
}

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8bb7a885-d762-4b7c-8a1a-d7d068ec75ab",
      "service": "bank_transfer_aggregated_php_hpp",
      "currency": "PHP",
      "amount": 510,
      "metadata": {
        "ip": "123.123.123.123"
      },
      "service_fields": {
        "first_name": "John",
        "last_name": "Doe",
        "phone": "+0123123123",
        "email": "test@mail.com"
      }
    }
  }
}

Important

  • service follows the pattern bank_transfer_aggregated_<currency>_hpp, where <currency> is php, thb or vnd.
  • service_fields.first_name, .last_name, .phone and .email are passed on to Payment Asia's hosted page as-is for all three currencies.

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 -> Corefy falls back to a built-in default

Currently available constants (constant -> Corefy API field)

  • CUSTOMER_IP -> metadata.ip - available per currency (PHP, THB, VND); if neither the request field nor the constant is set, Corefy falls back to a fixed default value of 127.0.0.1

Refunds

Payment Asia does not support refunds through this connector.

Payouts processing (connect Provider account, create payout-invoice)

Connect Provider account in Corefy Dashboard

Uses the same Provider account connected above - no separate connection step.

First request to Corefy API (MIN)

What it does: creates a payout-invoice for a bank-transfer payout. Payout methods cover a wide range of banks and e-wallets in Vietnam (VND), Thailand (THB) and the Philippines (PHP).

Payout - MIN

POST /api/payout-invoices 

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "f03d9793-39c2-4398-9e7f-53c5f502f0e2",
      "service": "robinsons_bank_php",
      "currency": "PHP",
      "amount": 500,
      "fields": {
        "bank_account_number": "1234567890",
        "beneficiary_first_name": "John",
        "beneficiary_last_name": "Doe"
      }
    }
  }
}

Payout - MAX

POST /api/payout-invoices 

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "6be05631-8710-4b14-a369-1928a2b70eda",
      "service": "robinsons_bank_php",
      "currency": "PHP",
      "amount": 500,
      "fields": {
        "bank_account_number": "1234567890",
        "beneficiary_first_name": "John",
        "beneficiary_last_name": "Doe",
        "beneficiary_phone": "+639171234567",
        "beneficiary_email": "test@mail.com"
      }
    }
  }
}

Important

  • fields.bank_account_number is required for every payout method; fields.beneficiary_phone/.beneficiary_email are optional.
  • The field used for the beneficiary's name depends on the selected service (bank/method): most Thai and Philippine banks, plus a handful of Vietnamese banks, expect separate fields.beneficiary_first_name/fields.beneficiary_last_name (as in the example above); most other Vietnamese bank methods instead expect a single combined fields.customer_name, which Corefy automatically splits into first/last name before sending it to Payment Asia. If you're not sure which one your chosen service expects, check with your Corefy account manager.
  • If a beneficiary full name isn't supplied directly, Corefy builds one from the first/last name fields before sending the request.

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

Not applicable - Payment Asia payouts are one-way disbursements.

Additional info

  1. No recurring - this connector does not support saving/charging a token through Corefy.
  2. Active reconciliation is available on both Payments and Payouts - besides the asynchronous callback, Corefy can actively query Payment Asia for the current status of a payment or a payout.
  3. Both Payments and Payouts receive an asynchronous server-to-server callback from Payment Asia; each callback's signature is verified using a SHA-512 hash of the sorted request parameters plus your Secret Code.
  4. All outgoing requests to Payment Asia are signed the same way - a SHA-512 hash of the sorted request parameters plus your Secret Code.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify Merchant ID, Merchant Token and Secret Code are correct and match the connected account
  • Currency or service is not supported -> confirm the currency/bank combination is enabled on your Payment Asia account and available in Corefy
  • Signature mismatch on callback -> make sure the Secret Code configured in Corefy matches the one on your Payment Asia account
  • Wrong beneficiary name field for a payout -> check whether your chosen payout service expects separate first/last name fields or a single combined name field (see Payouts above)
  • Need a refund -> not available for this connector; contact Payment Asia directly if a reversal is needed

Question

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