FYST¶

Website: fyst.com

Set up Account H2H merchant account¶

Step 1: Create Merchant Account¶

To create an account send connection request at the fyst.com/contact-us 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:

• fyst__login → Login
• fyst__control_key → Control key
• fyst__endpoint_id → Endpoint ID
• fyst__test_mode → Test mode
• fyst__multi_currency_integration → Multi Currency Integration
• fyst__currency → choose currency (You can set these parameters according to available currencies and features for your FYST wallets and services, but it's necessary to check details of the connection with your Corefy account manager.)

Connect Merchant Account¶

Step 1. Connect H2H account at the Corefy Dashboard¶

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

Enter credentials:

• Login
• Control key
• Endpoint ID
• Test mode → true/false
• Multi Currency Integration

Set up Account Provider account¶

Step 1: Create Provider account¶

To create an account send connection request at the fyst.com/start-now 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:

• fyst__login → Login
• fyst__private_key → Private key
• fyst__control_key → Control key
• fyst__endpoint_id → Endpoint ID
• fyst__test_mode → Test mode
• fyst__multi_currency_integration → Multi Currency Integration

Connect Provider Account¶

Step 1. Connect Provider account at the Corefy Dashboard¶

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

Enter credentials:

• Login
• Private key
• Control key
• Endpoint ID
• Test mode → true/false
• Multi Currency Integration

API examples:¶

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

SALE

POST /api/payment-invoices HTTP/1.1
{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "882f2326-0451-473a-9c43-3c6b1b8997e9",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 1,
      "customer": {
        "reference_id": "user1",
        "name": "Test test",
        "email": "[email protected]",
        "phone": "+4444444444",
        "address": {
          "full_address": "Test addr",
          "country": "DE",
          "city": "TestCity",
          "post_code": "AA123"
        }
      }
    }
  }
}

Maximum data set to create a payment invoices for payment_card_eur_hpp service¶

SALE

POST /api/payment-invoices HTTP/1.1
{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "882f2326-0451-473a-9c43-3c6b1b8997e9",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 1,
      "customer": {
        "reference_id": "user1",
        "name": "Test test",
        "email": "[email protected]",
        "phone": "+4444444444",
        "address": {
          "full_address": "Test addr",
          "country": "DE",
          "region": "TestState",
          "city": "TestCity",
          "street": "Test street",
          "post_code": "AA123"
        }
      }
    }
  }
}

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

PAYOUT

POST /api/payout-invoices HTTP/1.0
{
  "data":{
    "type":"payout-invoice",
    "attributes":{
      "reference_id":"7ae1fb60-9651-454f-9c1a-bca0f57a26b0",
      "service":"payment_card_usd",
      "commerce_account":"hello_world",
      "currency":"USD",
      "amount":3,
      "customer":{
        "reference_id":"tesf231",
        "name":"John Doe",
        "first_name":"John",
        "surname":"Doe"
      },
      "test_mode":true,
      "fields": {
        "card_number": "400000******0002"
      }
    }
  }
}

Provider Options¶

• Ignore callback
  • for cascading to work correctly, we exclude the possibility of finalizing payments using asynchronous callbacks, ignore the callback, do not change the status of the transaction on it in any way and rely only on the status request for finalization (Reconciliation)
• Use default browser info
  • if option = true → constants for browser-date are used
• Custom finalization logic
  • it will be possible to dynamically manage the map
    • if option = true and status is successful → then we finalize in success ignoring error resolution.
    • if option = false → we follow the default flow, where we will take into account error resolution.