Authorizations
Admin API keys allow you to perform some privileged actions such as creating a merchant account and Connector account.
Path Parameters
The unique identifier for the Merchant Connector
Body
Create a new Merchant Connector for the merchant account. The connector could be a payment processor / facilitator / acquirer or specialized services like Fraud / Accounting etc."
Type of the Connector for the financial use case. Could range from Payments to Accounting to Banking.
payment_processor
, payment_vas
, fin_operations
, fiz_operations
, networks
, banking_entities
, non_banking_finance
, payout_processor
, payment_method_auth
, authentication_processor
, tax_processor
, billing_processor
, vault_processor
inactive
, active
The identifier for the Merchant Account
1 - 64
"y3oqhf46pyzuxjbcn2giaqnb44"
This is an unique label you can generate and pass in order to identify this connector account on your Hyperswitch dashboard and reports, If not passed then if will take connector_name
_profile_name
. Eg: if your profile label is default
, connector label can be stripe_default
"stripe_US_travel"
An object containing the details about the payment methods that need to be enabled under this merchant connector account
You can specify up to 50 keys, with key names up to 40 characters long and values up to 500 characters long. Metadata is useful for storing additional, structured information on an object.
A boolean value to indicate if the connector is disabled. By default, its value is false.
false
Contains the frm configs for the merchant connector
"\n[{\"gateway\":\"stripe\",\"payment_methods\":[{\"payment_method\":\"card\",\"payment_method_types\":[{\"payment_method_type\":\"credit\",\"card_networks\":[\"Visa\"],\"flow\":\"pre\",\"action\":\"cancel_txn\"},{\"payment_method_type\":\"debit\",\"card_networks\":[\"Visa\"],\"flow\":\"pre\"}]}]}]\n"
pm_auth_config will relate MCA records to their respective chosen auth services, based on payment_method and pmt
Feature metadata for merchant connector account
Response
Merchant Connector Updated
Response of creating a new Merchant Connector for the merchant account."
Type of the Connector for the financial use case. Could range from Payments to Accounting to Banking.
payment_processor
, payment_vas
, fin_operations
, fiz_operations
, networks
, banking_entities
, non_banking_finance
, payout_processor
, payment_method_auth
, authentication_processor
, tax_processor
, billing_processor
, vault_processor
authipay
, adyenplatform
, stripe_billing_test
, phonypay
, fauxpay
, pretendpay
, stripe_test
, adyen_test
, checkout_test
, paypal_test
, aci
, adyen
, affirm
, airwallex
, amazonpay
, archipel
, authorizedotnet
, bambora
, bamboraapac
, bankofamerica
, barclaycard
, billwerk
, bitpay
, bluesnap
, blackhawknetwork
, bluecode
, boku
, braintree
, breadpay
, cashtocode
, celero
, chargebee
, checkbook
, checkout
, coinbase
, coingate
, custombilling
, cryptopay
, ctp_mastercard
, ctp_visa
, cybersource
, datatrans
, deutschebank
, digitalvirgo
, dlocal
, dwolla
, ebanx
, elavon
, facilitapay
, fiserv
, fiservemea
, fiuu
, flexiti
, forte
, getnet
, globalpay
, globepay
, gocardless
, gpayments
, hipay
, helcim
, hyperswitch_vault
, inespay
, iatapay
, itaubank
, jpmorgan
, juspaythreedsserver
, klarna
, mifinity
, mollie
, moneris
, multisafepay
, netcetera
, nexinets
, nexixpay
, nmi
, nomupay
, noon
, nordea
, novalnet
, nuvei
, opennode
, paybox
, payload
, payme
, payone
, paypal
, paysafe
, paystack
, paytm
, payu
, peachpayments
, phonepe
, placetopay
, powertranz
, prophetpay
, rapyd
, razorpay
, recurly
, redsys
, santander
, shift4
, silverflow
, square
, stax
, stripe
, stripebilling
, taxjar
, threedsecureio
, tokenio
, trustpay
, tsys
, vgs
, volt
, wellsfargo
, wise
, worldline
, worldpay
, worldpayvantiv
, worldpayxml
, signifyd
, plaid
, riskified
, xendit
, zen
, zsl
Unique ID of the merchant connector account
"mca_5apGeP94tMts6rg3U3kR"
Identifier for the profile, if not provided default will be chosen from merchant account
64
An object containing the details about the payment methods that need to be enabled under this merchant connector account
inactive
, active
A unique label to identify the connector account created under a profile
"stripe_US_travel"
Metadata is useful for storing additional, unstructured information on an object.
A boolean value to indicate if the connector is disabled. By default, its value is false.
false
Contains the frm configs for the merchant connector
"\n[{\"gateway\":\"stripe\",\"payment_methods\":[{\"payment_method\":\"card\",\"payment_method_types\":[{\"payment_method_type\":\"credit\",\"card_networks\":[\"Visa\"],\"flow\":\"pre\",\"action\":\"cancel_txn\"},{\"payment_method_type\":\"debit\",\"card_networks\":[\"Visa\"],\"flow\":\"pre\"}]}]}]\n"
identifier for the verified domains of a particular connector account
pm_auth_config will relate MCA records to their respective chosen auth services, based on payment_method and pmt
Feature metadata for merchant connector account