Authorization Configurations

system wide configuration upstart commerce allows you to configure multiple payment service providers (psps) for payment authorization this configuration enables you to set up a robust payment processing system with failover capabilities payment service provider (psp) configuration when you set up a payment service provider in upstart commerce, you're essentially telling the system how to connect with a company that will process payments for your online store here's a breakdown of what you'll need to set up, using a fictional payment provider called "securepay" as an example provider name this is simply what you call this payment setup for example, "securepay main account" your store details store name "cozy home furnishings" website "cozyhome com" which of your online stores will use this you might have multiple online stores you can choose which ones will use this payment method for example, "cozy home us site" and "cozy home canada site" securepay account details account type "test account" (for trying things out) or "live account" (for real transactions) your securepay id something like "cozyhome123" security file a special file securepay gives you, like "cozyhome123 secret" how important is this payment method priority 1 (this means it's your first choice for processing payments) partial payments yes (this allows customers to split payments if needed) safety net settings these help protect your store if there are problems with securepay max failures 3 (if securepay fails 3 times in a row, stop using it temporarily) wait time 10 seconds (how long to wait for securepay to respond) cooldown time 15 seconds (how long to wait before trying securepay again after failures) is it ready to use turned on yes you can set up multiple payment providers if you do, the system will use them in order of priority so if your number 1 choice has problems, it will automatically try your number 2 choice, and so on this helps ensure your customers can always complete their purchases by configuring multiple psps with different priorities, you ensure continuous payment processing capabilities, enhancing the reliability of your e commerce platform pre order functionality (tenant level) pre order refers to a system for handling payment processing when a psp is unavailable, not the traditional definition of ordering products before they're available this configuration enables you to decide if the system should create a pre order if the psp is unavailable during authorization with pre order enabled, if the psp is not accessible, the customer's cart will be submitted, and the order will go into a queue the queue will then process the payment attempt later when the psp becomes available curl location 'http //api upstartcommerce com/payment processing/cfg/records' \\ \ header 'x upstart tenant apparelstore' \\ \ header 'content type application/json' \\ \ header 'authorization bearer your access token here' \\ \ data '{ "recordid" "preorder", "name" "preorder as", "templateid" "preorder", "tenant" "apparelstore", "domain" "paymentprocessing", "siteids" \[ "site id 1", "site id 2" ], "tags" \[], "data" { "preorderenable" true, "linkexpirationtime" 172800 }, "enabled" true }' here's an example of using pre order functionality imagine your primary psp is down for maintenance during peak hours a customer tries to purchase a limited edition designer jacket from your store if pre order is enabled, the customer's order will still be submitted and placed in a queue, despite the psp being unavailable once the psp comes back online, the queued order will be processed automatically this ensures you don't lose sales due to temporary psp outages queuing scheduler configuration a queuing scheduler configuration to manage the processing of queued orders this configuration defines the frequency at which the system processes queued payments the cron pattern determines the schedule for processing, ensuring efficient handling of queued transactions curl location 'http //localhost 8085/payment processing/cfg/records' \\ \ header 'x upstart tenant apparelstore' \\ \ header 'content type application/json' \\ \ header 'authorization bearer your access token here' \\ \ data '{ "recordid" "paymentsqueuescheduler 001", "tenant" "apparelstore", "domain" "paymentprocessing", "templateid" "paymentsqueuescheduler", "siteids" \[ "site id 1", "site id 2" ], "tags" \[], "name" "paymentsqueuescheduler", "data" { "cronpattern" "0 0/1 1/1 ? " }, "enabled" true }' payment set restriction currently, upstart commerce doesn't allow using multiple psps for authorization if you're using cybersource as your payment processor you'll need to choose and configure a single cybersource connection for authorization