Procard.Pay¶

Website: procard.ua

Set up Account H2H merchant account¶

Step 1: Create Merchant Account¶

To create an account send connection request at the procard.ua/#contacts or contact manager directly. Submit the required documents to verify your account and gain access.

Step 2: Get required credentials¶

Credentials that have to be issued:

• merchant_id → Merchant ID
• private Key → Private Key
• api_url → Api Url
• test_mode = true/false
• currency → choose currency (You can set these parameters according to available currencies and features for your Procard.Pay wallets and services, but it's necessary to check details of the connection with your Corefy account manager.)

How Test mode and Api Url works?¶

• When Test mode and Api Url are included
• Excluded Test mode and continue the Api Url inscribed = Production environment
• Api Url is not an enpoint

Connect Merchant Account¶

Step 1. Connect H2H account at the Corefy Dashboard¶

Press Connect at Procard.Pay Provider Overview page in 'New connection' section and choose H2H Merchant account option to open Connection form.

Enter credentials:

• Merchant ID
• Private Key
• Api Url

Set up Account Provider account¶

Step 1: Create Provider account¶

To create an account send connection request at the procard.ua/#contacts or contact manager directly. Submit the required documents to verify your account and gain access.

Step 2: Get required credentials¶

Credentials that have to be issued:

• merchant_id → Merchant ID
• private Key → Private Key
• api_url → Api Url

Connect Provider Account¶

Step 1. Connect Provider account at the Corefy Dashboard¶

Press Connect at Procard.Pay Provider Overview page in 'New connection' section and choose Provider account option to open Connection form.

Enter credentials:

• Merchant ID → Merchant ID
• Private Key → Private Key
• Api Url → Api Url

How Test mode and Api Url works?¶

• When Test mode and Api Url are included
• Excluded Test mode and continue the Api Url inscribed = Production environment
• Api Url is not an enpoint

API examples:¶

Minimum data set to create a payment invoices for payment_card service¶

SALE

POST /api/commerce/payment-invoices HTTP/1.0
{
  "data":{
    "type":"payment-invoice",
    "attributes":{
      "service":"payment_card_uah_hpp",
      "commerce_account":"Hello_World",
      "currency":"UAH",
      "amount":2,
      "reference_id":"a68fd4db-7a55-48bf-aa99-ee31b15160e8",
      "flow":"charge",
      "gateway_options":{
        "cardgate":{
          "tokenize":""
        }
      },
      "test_mode":true,
      "options":{
        "allow_partially":false,
        "bypass_hpp":false,
        "send_operation_context_on_return":false
      },
      "service_fields":[
      ]
    }
  }
}

Minimum data set to create a payout invoices for card_uah service¶

PAYOUT

POST /api/commerce/payout-invoices HTTP/1.0
{
  "data":{
    "type":"payout-invoice",
    "attributes":{
      "service":"payment_card_uah",
      "commerce_account":"Hello_World",
      "currency":"UAH",
      "amount":12,
      "reference_id":"84a1e92f-e5d3-4eec-95d1-9c7c4d16175f",
      "customer":{
        "reference_id":"a2a0f28e-0a54-426c-91d0-bd183a604832",
        "name":"John Doe Doevich"
      },
      "test_mode":false,
      "fields":{
        "card_number":"555555******5557"
      },
      "options":{
        "attempts_limit":0,
        "split_mode":false,
        "allow_partially":false,
        "auto_process":false
      }
    }
  }
}

Provider Options¶

• use_reverse
  • If this option is enabled, we will use endpoint => /reverse for the reverse transaction
  • If this option is disabled, we will use endpoint => /refund for the refund transaction