Create Application - Sub-Merchant Card Not Present

Create an application for a sub-merchant that does not require a physical card for their transactions. This is usually a merchant that has an online business.

Nota

In order to create a submerchant application, its parent application should have been already created. See also:

Parameters

Request Header Parameters

- access_key
- Unique access key provided by Rapyd for each authorized user.
  See Desarrolladores.
- Content-Type
- Indicates that the data appears in JSON format. Set to application/json.
- idempotency
- A unique key that prevents the platform from creating the same object twice.
  See Idempotency.
- salt
- Random string. Recommended length: 8-16 characters.
- signature
- Signature calculated for each request individually.
  See Request Signatures.
- timestamp
- Timestamp for the request, in Unix time (seconds).
- merchant_account_id
- The merchant account ID that was provided to you when you created the organization. See also Create Organization.

Request Body Parameters

Response Parameters

- token
- Identifier of the application. String starting with app_.

- version
- The version number of the application. The version is incremented by 1 each time it is updated.

- status
- The following statuses of the application are available:
  - New: Application was created but not yet submitted.
  - Submitted: Application has been submitted. All required fields were completed.
  - Pending Review: An application is waiting in the queue to be reviewed.
  - In Review: An application is being reviewed by a CompOps Analyst.
  - Approved: Application has been approved, either manually or automatically.
  - Limited Approval: Application was approved with limits, either manually or automatically.
  - Rejected: Application was rejected, either manually or automatically.
  - BACKLOG: If there is a technical issue, then the application is in backlog status, and an attempt to rerun the application will be made when the technical issue is resolved.

- ewallet_token
- The eWallet of the merchant. String starting with ewallet_.

- metadata
- A JSON object defined by the client. See Metadata

- entity_type
- The type of entity:
  - Sole Proprietor Card Present
  - Sole Proprietor Card Not Present
  - Non-Sole Proprietor Card Present
  - Non-Sole Proprietor Card Not Present

- country
- The two letter country code of the entity. Uppercase.

- created_at
- Time of creation of the object, in Unix time.

- updated_at
- Time of the last update of the object, in Unix time.

- sell_type
- The description of the sell type. See also List Industries
  - Card Present - Physical Business (Brick and Mortar)
  - Card Not Present - Website with a Checkout Page

- business_industry
- Four digit merchant category code of the business industry. See also List Industries

- sections
- Includes the sections of the application with the current field values.
  business
  Business-related information section.
  url
  URL object.
  business_url
  The URL of the business’s website.

- link
- Link to a hosted page where the application can be filled out online.

- merchant_phone_number
- Phone number details of the merchant.
  phone_country_code
  The two-letter ISO 3166-1 ALPHA-2 code for the country of the phone number.
  phone_number
  The phone number of the merchant without the international phone code.

- instructions
- Includes the instructions on how to fill out the application. Certain industry types enable filling out the application via the APIs and a link to hosted page. However, there are industry types that do not enable filling out the application via API methods and require filling it out via a hosted page link. In such scenarios the application is not returned and the following instructions are displayed: "The industry type for this application must filled out online. "

- parent_application_token
- Identifier of the parent application. String starting with app_.

Each section includes unique required and optional fields. A field includes the issues object in cases where its value of is missing or is invalid. The issues object includes the fieldname and the details for providing the correct value. For example, if an invalid value is provided for the business_name field, then details are "Enter a value of up to 80 alphanumeric characters and spaces."

If a required field value is entered correctly then the field displays its current value and it has a no issues object.

/v1/partner/onboarding/application/sub_merchant

Create Application - Sub-Merchant Card Not Presentt

curl -X post
'https://api.rapyd.net/v1/partner/onboarding/application/sub_merchant' \
-H 'access_key: your-access-key-here' \
-H 'Content-Type: application/json' \
-H 'idempotency: your-idempotency-parameter-here' \
-H 'salt: your-random-string-here' \
-H 'signature: your-calculated-signature-here' \
-H 'timestamp: your-unix-timestamp-here' \
-H 'merchant_account_id: your-merchant-account-here' \
--data-raw ' {
  "business_industry": "4814",
  "sell_type": "card_not_present",
  "sections": {
    "business": {
      "url": {
        "business_url": "https://www.example1234.com"
      }
    }
  }
}
'

{
    "status": {
        "error_code": "",
        "status": "SUCCESS",
        "message": "Success",
        "response_code": "",
        "operation_id": "177d773e-9d1d-43b2-90a7-a725930a6ffa"
    },
    "data": {
        "token": "app_311ea429a09042889c573caf98278203",
        "version": 2,
        "status": "NEW",
        "ewallet_token": "ewallet_50519d74b03dc39a2f3903ce8b2b9f17",
        "metadata": {},
        "entity_type": "Partnership",
        "country": "AR",
        "created_at": 1772976210803,
        "updated_at": 1772976211805,
        "sell_type": "Website with a Checkout Page",
        "business_industry": 4814,
        "sections": {
            "business": {
                "url": {
                    "business_url": "https://www.example1234.ecom"
                }
            }
        },
        "link": "https://qaverify.rapyd.net/verify?token=happ_f9f11295f3f84ec79fa86a811f4ca646",
        "merchant_phone_number": null,
        "instructions": null,
        "parent_application_token": "app_8ca4baed04d74b6d9087fce547940ef4"
    }
}

En esta sección:

Documentación