v1
latestOpenAPI 3.0.22026-08-061303782.1 MBCreate a Merchant
Create a Merchant to start the underwriting (also called provisioning) process for your seller. Merchants must be created under an Identity.
A bank account must be associated with the previously created Identity before a Merchant can be successfully onboarded and verified.
Headers
Specify the API version of your request. For more details, see Versioning.
The data type being sent in the request body must be application/json.
Request body
- Set to true if you want to enable partial authorizations for a specific Merchant.
- Partial authorizations enable the Merchant to collect a portion of the amount if the cardholder doesn't have the funds to cover the entire amount on their card.
Set to true to enable the Merchant to process debt loan repayment. Only MCCs 6012 and 6051 are eligible.
Set the acquiring processor. Use DUMMY_V1 or null for your Sandbox. For more details on which processor to use, reach out to your Finix point of contact or email Finix Support.
A value of true disables refunds for the Merchant, including both referenced and unreferenced refunds.
Include up to 50 key: value pairs to annotate requests with custom metadata.
- Maximum character length for individual keys is 40.
- Maximum character length for individual values is 500. (For example, order_number: 25, item_type: produce, department: sales)
Response
Single Merchant object
The ID of the resource.
Timestamp of when the object was created.
Timestamp of when the object was last updated.
ID of the Application associated with the resource.
Set to true to require the card's CVV code.
Set to true to require the card's expiration date.
Set to true if you want to enable the Merchant to accept convenience fees and/or service fees.
Set to true to automatically create Transfers once settlement reports get generated.
ISO 4217 3-letter currency code.
- Set to true if you want to enable partial authorizations for a specific Merchant.
- Partial authorizations enable the Merchant to collect a portion of the amount if the cardholder doesn't have the funds to cover the entire amount on their card.
Indicates whether same-day ACH pull disbursements (debits) are enabled, allowing funds to be withdrawn from an account via same-day ACH transfer.
Indicates whether same-day ACH push disbursements (credits) are enabled, allowing funds to be sent to an account via same-day ACH transfer.
Details how the Merchant settles fees.
This field shows the timestamp when the Merchant was first approved. If the Merchant has not been approved yet, the value is null.
Set to true to enable gross settlements.
The ID of the Identity resource associated with the Merchant.
Set to true if you want to allow the merchant to be enabled for settlement instant payouts.
Set to true to terminate the Merchant. A merchant can only be terminated if its current onboarding_state is APPROVED.
Set to true to enable the Merchant for Level 2 and Level 3 processing. Default value is false.
Whether the merchant is able to support loan repayment on the card networks.
The Merchant Category Code (MCC) that this merchant will be classified under. For a list of approved MCCs, see Approved Merchant Category Codes.
The legal name saved in the Merchant resource.
Details if a merchant's info was submitted to third-party processors for provisioning.
MID of the Merchant.
Details the state of the Merchant's onboarding.
Details if transaction processing is enabled for the Merchant. ROLE_PARTNER can only set this value to false.
Name of the transaction processor.
Details how transactions captured by the Merchant are settled.
Indicates whether transaction settlement should be delayed to synchronize the timing of all transactions, including both card and ACH, ensuring they are settled together.
Possible values include:
- ACH - Align all transactions to match the timing of ACH settlements, so card transactions settle at the same speed as ACH transactions.
- NONE - Default behavior where card transactions settle the next day (T+1) and ACH transactions settle two days later (T+2).
A value of true disables refunds for the Merchant, including both referenced and unreferenced refunds.
Set to true if you want to enable a Merchant to accept rent charges.
Details if settlement approvals are enabled for the Merchant. ROLE_PARTNER can only set this value to false.
Includes additional information (like the MID or Merchant name) when submitting funding Transfers to processors.
- UNSET: No additional details get provided to the processor.
- MID_AND_DATE: The MID of the Merchant and the date the funding Transfer was submitted (Date is in UTC). e.g MID:12345678-20220225
- MID_AND_MERCHANT_NAME: The MID of the Merchant and the Merchant#name (white spaces will be removed). e.g. MID:12345678-NameOfMerchant
These details appear alongside the seller's payout in their bank account as a description of the deposit.
If settlement_queue_mode is set to MANUAL, Finix will automatically place all transactions (Sales, Fees, Refunds, and ACH Returns) into a settlement queue that you can manage. Each transaction will have a Settlement Queue Entry.
When a Settlement Queue Entry is created, it will not be placed into Settlement until the Settlement Queue Entry is explicitly released.
Note: We require the release of all settlement queue entries within 30 days of creation.
Set to true if you want to enable a Merchant to accept surcharge fees. For more details, see Buyer Charges.
Include up to 50 key: value pairs to annotate requests with custom metadata.
- Maximum character length for individual keys is 40.
- Maximum character length for individual values is 500. (For example, order_number: 25, item_type: produce, department: sales)
Indicates if merchant is allowed to process unreferenced refunds initiated through manual card entry on Finix terminals.
ID of the Verification that was submitted to verify the Merchant.
Example response
{
"termination_details": {
"terminated_at": "2024-09-16T13:11:36.72Z"
}
}