{"info":{"_postman_id":"761f7378-b500-44c8-839b-304826336f93","name":"Shuttle - Legacy","description":"

This document contains documentation for LEGACY version of the APIs.

Please see api.shuttleglobal.com for the latest APIs.

\n","schema":"https://schema.getpostman.com/json/collection/v2.0.0/collection.json","toc":[],"owner":"6049226","collectionId":"761f7378-b500-44c8-839b-304826336f93","publishedId":"SzfCU61V","public":true,"customColor":{"top-bar":"FFFFFF","right-sidebar":"303030","highlight":"EF5B25"},"publishDate":"2020-04-27T11:36:51.000Z"},"item":[{"name":"payments.js - v1.0.X","item":[{"name":"Onboarding / Setup Popover","item":[],"id":"d421dd84-2daf-40e3-8cca-1c6798b29adc","description":"

To allow a merchant to SaaS Checkout for their gateway, add a “Configure Payments” button or hyperlink on your settings page. The recommended button approach will pre-load assets to make the user experience more seamless, whereas the Javascript function will start loading assets when called.

Body can either be serialised as a string or serialised as base64. If serialising as a string be careful to escape any quotes in the string.

Note: If instance_key has no associated account, the merchant will be presented a T&Cs screen to agree to. Once agreed a new account will be provisioned for them to configure. If the merchant already has an account, they will be taken straight to the setup screen.

Try it now: JSFiddle

Options

var options = {\n    instance_key: \"10000\",\n    company_name: \"Dave's Bakery\",\n    company_country: \"US\",\n    contact_name: \"David Smith\",\n    contact_email: \"david@davesbakery.com\",\n    contract_phone: \"447985918872\"\n};\n

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n

Field	Description
`instance_key`	the unique instance_key identifying the merchant / client, in general this will be `merchant_id` or `your_environment_name + merchant_id` eg `1` or `PROD_1`
`company_name`	(optional) the name of the merchant - this will be prompted for if not passed
`company_country`	(optional) the 2 letter country code of the merchant - this will be prompted for if not passed
`contact_name`	(optional) the name of the primary contact - this will be prompted for if not passed
`contact_email`	(optional) the contact email of the primary contact - this will be prompted for if not passed
`contact_phone`	(optional) the contact phone of the primary contact - this will be prompted for if not passed
`receipt_format`	(optional) the format for receipt ID generation, by default this is `BOLT-#TRANSACTIONKEY#`, please be sure to include `#TRANSACTIONKEY#` in the format to ensure receipts are always unique.
`locale`	(optional) the 2 letter language code or full locale (eg en or en_US). If you pass this, this locale will be used in the popover, otherwise it will use the browsers locale, or IP lookup where no browser locale. If the language is not available, the default language will be returned. Typically this is English, however you can customise it.
`no_redirect`	(available in `payments-1.0.10`) true / false: disable redirecting to the setup process on mobile devices. Typically on mobile devices, rather than a popover, the user is redirected to the setup process and on close, redirected back to the page they were on. This is to overcome poor performance of mobile devices showing full screen iframes over existing websites. This parameter will disable this behaviour.

Method

To use button DOM attributes, you will need to populate:

data-bolt-setup: With the serialised options
data-bolt-signature: With the signature

eg <button data-bolt-setup=\"options\" data-bolt-signature=\"signature\"></button>

for Javascript, call:

var options = {...};\nvar signature = generateSignature(options);\n// Note: signature generation should be server side,\n// never pass your secret-key to the client browser \n\nBolt.saas.doSetup(options, signature);\n

","event":[{"listen":"prerequest","script":{"id":"8eafe6cf-c24f-4129-82d2-a5be1b2456c8","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"998c7d01-c38c-4e4e-a28c-10b0a6dfddbb","type":"text/javascript","exec":[""]}}],"_postman_id":"d421dd84-2daf-40e3-8cca-1c6798b29adc","auth":{"type":"basic","basic":{"basicConfig":[{"key":"username","value":"{{session_key}}"}]},"isInherited":true,"source":{"_postman_id":"761f7378-b500-44c8-839b-304826336f93","id":"761f7378-b500-44c8-839b-304826336f93","name":"Shuttle - Legacy","type":"collection"}}},{"name":"Payment Popover","item":[],"id":"ea074e2c-77e3-4b7d-a5af-afc71451fcbd","description":"

The payment popover works the same way as onboarding, simply contruct your options and signature. Note you can pass a success_url which will redirect the browser to a new URL on successful payment, or catch the javascript window message.

Try it now: JSFiddle

Options

var options = {\n    instance_key: \"10000\",\n    amount: \"100\",\n    currency: \"USD\"\n};\n

Where options supports:

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n

Field Description

... All parameters from the REST API except payment_method - this must be selected by the user. You do not not need to nest within a payment tag (optional)

no_redirect (available in payments-1.0.10) true / false: disable redirecting to the payment process on mobile devices. Typically on mobile devices, rather than a popover, the user is redirected to the payment process and on close, redirected back to the page they were on. This is to overcome poor performance of mobile devices showing full screen iframes over existing websites. This parameter will disable this behaviour.

Field	Description
`...`	All parameters from the REST API except `payment_method` - this must be selected by the user. You do not not need to nest within a `payment` tag (optional)
`no_redirect`	(available in `payments-1.0.10`) true / false: disable redirecting to the payment process on mobile devices. Typically on mobile devices, rather than a popover, the user is redirected to the payment process and on close, redirected back to the page they were on. This is to overcome poor performance of mobile devices showing full screen iframes over existing websites. This parameter will disable this behaviour.

Method

To use button DOM attributes, you will need to populate:

data-bolt-payment; With the serialised options
data-bolt-signature: With the signature

eg <button data-bolt-payment=\"options\" data-bolt-signature=\"signature\"></button>

for Javascript, call:

var options = {...};\nvar signature = generateSignature(options);\n// Note: signature generation should be server side,\n// never pass your secret-key to the client browser \n\nBolt.saas.doPayment(options, signature);\n

","event":[{"listen":"prerequest","script":{"id":"ba36c7bd-4df5-4cfe-9c8c-9b2cfd080e8f","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"9e625b08-d4ad-4988-a19b-8b954b159b4e","type":"text/javascript","exec":[""]}}],"_postman_id":"ea074e2c-77e3-4b7d-a5af-afc71451fcbd","auth":{"type":"basic","basic":{"basicConfig":[{"key":"username","value":"{{session_key}}"}]},"isInherited":true,"source":{"_postman_id":"761f7378-b500-44c8-839b-304826336f93","id":"761f7378-b500-44c8-839b-304826336f93","name":"Shuttle - Legacy","type":"collection"}}},{"name":"Window Events","item":[],"id":"8df14ef1-abcc-405f-816a-d8aadb2aabbb","description":"

The following events are raised by the popover:

PAYMENT_CLOSE: Raised by both \"Setup\" and \"Payment\" whenever the popover is closed, you may wish to use this trigger to check the status of setup / payment and perform subsequent logic.
PAYMENT_SUCCESS: Raised by \"Payment\" whenever a payment is successfully \"processed\". Please note, in this context, the event will be raised if a recurring schedule created and no initial payment processed, and also if a payment is submitted for processing but still in a PENDING or UNRESOLVED status. As such its recommended to use this trigger to fetch the payment (using the alt_key you used to submit the payment) and decide your subsequent logic based on status. This event is raised PRIOR to the close of the popover so take into consideration if navigating away from the page.

An example of catching window events is included below:

window.addEventListener(\"message\", function(e) {\n    var payload = typeof e.data == \"string\" ? JSON.parse(e.data) : e.data;\n  \n    if (payload.message) {\n        console.log(\"Event: \" + payload.message);\n    }\n});\n

Where:

Its possible for other code / browser extensions to raise their windows messages, as such always check for the message type.
e.data should always be an object, however for backwards compatibility its recommended to also support the serialised form as shown above.

\n","event":[{"listen":"prerequest","script":{"id":"9b16cf3d-0064-4125-9cd3-9ca4d7d626d6","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"6e3907ec-097e-40e6-821e-d23758baec7d","type":"text/javascript","exec":[""]}}],"_postman_id":"8df14ef1-abcc-405f-816a-d8aadb2aabbb","auth":{"type":"basic","basic":{"basicConfig":[{"key":"username","value":"{{session_key}}"}]},"isInherited":true,"source":{"_postman_id":"761f7378-b500-44c8-839b-304826336f93","id":"761f7378-b500-44c8-839b-304826336f93","name":"Shuttle - Legacy","type":"collection"}}}],"id":"15f70936-83b2-4f04-9cd8-e984e3c9fa9e","description":"

The client side library provides an onboarding / setup popover and a payment/checkout popover. The popover appears within your page as a translucent iFrame to provide segmentation of PCI DSS compliance responsibility away from your platform.

To use these popovers:

1. Include the Javascript Library

Include the following file on all pages you launch popups from:

<script src=\"https://payments.withbolt.com/b/web/s/payments-1.0.11.min.js\">

2. Decide if integrating via DOM Attributes or Javascript

Using button DOM attributes will bind the popup to the onClick event of the element, for example, the below button will trigger the popup when clicked, this is the recommended approach:

<button data-bolt-setup=\"options\" data-bolt-signature=\"signature\"></button>

Note: Button attributes are detected on page load, if you render the button on the page AFTER page load, call Bolt.saas.bindButtons(); after your render cycle.

Using the Javascript method will launch the popup immediately, however as it is not pre-loaded, will take longer to open, for example, Bolt.saas.doSetup(options, signature);

3. Construct the options for the popup

Options is a Javascript object containing the allowed parameters for the method.

When using with button attributes, you will need to stringify JSON.stringify(options);. Take care to escape any quotes in the string, or alternatively you can base64 encode it base64encode(JSON.stringify(options));.

We provides serverside SDKs to facilitate this.

4. \"Sign\" the request with a signature

The easiest way to create a signature is via the SDKs. To manually create a signature, follow the below:

Create a timestamp in ms from 1970 eg new Date().getTime() (it will be a 13 digit number eg 1571677967213)
Stringify your options, omitting host, and nonce eg var signatureBody = JSON.stringify(_.omit(options, \"host\", \"nonce\"));
MD5 the concatenation of timestamp + methodName + signatureBody + secret_key, where methodName is doSetup or doPayment, and secret_key is your app's secret key from the developer portal
Your signature is: shared_key + \"-\" + timestamp + \"-\" + md5, where shared_key is your app's shared key from the developer portal

We provides serverside SDKs to facilitate this.

5. Catch client side events

The popovers will communicate back to your app with client side Javascript window.postMessage notifications, for instructions on how to catch these, see here.

\n","event":[{"listen":"prerequest","script":{"id":"c53b81fd-c048-4828-8db9-7b6ce4dfc7f2","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"e116dada-e953-434c-8d01-5a26d6c81669","type":"text/javascript","exec":[""]}}],"_postman_id":"15f70936-83b2-4f04-9cd8-e984e3c9fa9e","auth":{"type":"basic","basic":{"basicConfig":[{"key":"username","value":"{{session_key}}"}]},"isInherited":true,"source":{"_postman_id":"761f7378-b500-44c8-839b-304826336f93","id":"761f7378-b500-44c8-839b-304826336f93","name":"Shuttle - Legacy","type":"collection"}}},{"name":"Old Releases > 12 months","item":[{"name":"20201214","item":[],"id":"88dd1293-e5fe-40d1-b493-48af1b097ca0","description":"

New Features

Sandbox Gateway

Added a card that emulates failed refunds

API

(enterprise) Added logout API

Improvements

Updated the UUID mechanism to generate more unique values

Bug Fixes

Fixed an issue with the Sandbox Gateway hosted payments emulator
Fixed an issue whereby a payment instruction specified at a higher precision than the currency's minimum unit was being rejected with \"Request Tampering\" (eg $1.234). This will now be passed through to the gateway.

\n","event":[{"listen":"prerequest","script":{"id":"dd895298-d88b-4407-9ef7-da96d7a8c466","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"08c0666d-105f-47d5-8deb-8188d15c584b","type":"text/javascript","exec":[""]}}],"_postman_id":"88dd1293-e5fe-40d1-b493-48af1b097ca0","auth":{"type":"basic","basic":{"basicConfig":[{"key":"username","value":"{{session_key}}"}]},"isInherited":true,"source":{"_postman_id":"761f7378-b500-44c8-839b-304826336f93","id":"761f7378-b500-44c8-839b-304826336f93","name":"Shuttle - Legacy","type":"collection"}}},{"name":"20201119","item":[],"id":"17c18760-bc2f-4d8e-892f-4e4dfc4693c8","description":"

New Features

API

Transactions now return:
- gateway_view_transaction for gateways that support it a link to the the processor's dashboard for this transaction
- expires if action = AUTH the date the authorisation expires (where known)
- refund if action == REFUND a link to the refund object
\n

Merchant View

Authorisations now display expiry dates (where available)
Transactions include links to the processort portal (where available)

Improvements

Instance name is now optional
You can now pass tags on the payment API in the account object
MOTO payments now prevent request tampering
\"Quickbooks Payments\" now allows you to tokenise payment methods under your existing Quicbooks user objects. Just pass the Quickbooks contact id as a tag on the account prefixed with QB- eg QB-12345 will link a Shuttle account and Quickbooks account 12345.

\n","event":[{"listen":"prerequest","script":{"id":"be718de2-5c22-418f-aabc-6a05a9ed9ad3","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"4ab535bd-256e-4571-a7bd-eb81f4969dba","type":"text/javascript","exec":[""]}}],"_postman_id":"17c18760-bc2f-4d8e-892f-4e4dfc4693c8","auth":{"type":"basic","basic":{"basicConfig":[{"key":"username","value":"{{session_key}}"}]},"isInherited":true,"source":{"_postman_id":"761f7378-b500-44c8-839b-304826336f93","id":"761f7378-b500-44c8-839b-304826336f93","name":"Shuttle - Legacy","type":"collection"}}},{"name":"20201115","item":[],"id":"117ce4fe-9a46-401d-90cb-ef5e52ba9d71","description":"

We've updated the developer portal to make it faster and easier to use, in addition we've added a number of new features and improvements outlined below.

One of the key changes is adding and editing an account is now separate from configuring a payment processor. This streamline the payment processor configuration. We've also embeded the upcoming payment configuration'

New Features

Application receipt format: Improve the branding of your app by controlling how transaction references are generated eg \"APPNAME-0000001\", you can also configure this on a merchant by merchant basis
\n
Merchant view customisation: Streamline your user's experience in the merchant view by removing unnecessary or unwanted features:
\n
- Recurring Payments: If your application does not use recurring payments, this will remove all references to them
  - Schedule Amendments: If you need schedule amendments to be instructed by your platform, you can remove manual amendmentsfrom the merchant view
  \n
- Staff payments: Remove the ability for staff to enter MOTO payments
- Staff payment method entry: Remove the ability for staff to enter payment method details
- Manual void / capture: Remove the ability for manually instructing a capture / void on an authorisation
- Staff refunds: Remove the ability to instruct a refund from the merchant view
- \"Offline\" refunds: Remove the ability to instruct a manual refund in the merchant view (meaning all refunds must be processed by the payment processor)
- Account add / edit: Remove the ability to add or edit account (customer) details in the merchant view
- Payment method edit / delete: Remove the ability to edit or delete a payment method's in the merchant view
- Comments: Remove the ability to make comments on objects (like contracts) in the merchant view
\n
Accounts Add: You can now create both Sandbox and Live accounts in the portal, along with their instance_key and receipt_format
\n
Account Edit: You can now edit both Sandbox and Live accounts in the portal, along with their
\n
- application: Move an instance between applications
- instance_key: Update the primary key of the instance
- receipt_format: Change how transaction references are generated
\n
Account Termination: You can now terminate instances directly from the portal, one by one or in bulk for sandbox accounts
\n
Billable Transactions: Each account now has a monthly graph of \"billable transactions\" to better understand platform usage
\n
Account View: We've created an account view embeding the Payment Configuration & Merchant View components to make it easier to use
\n
Payment processor configuration has seem a complete overhaul, with a brand new user experience. The intent is for this to supercede the current setup component in due course, however for now we are interested in user feedback.
\n
- Multi-Processor: Connect many payment processors, and decide how you want to ROUTE payment instructions into those payment processors
- Smart Checkout: Build a complex checkout by combining cards, ACH, SEPA, PayPal and many other payment types
- Payment Method Control: Enable / disable different methods of payment, or route through different processors, eg disable cards or ACH
- Run-down Processors: Change your primary cards processor, whilst retaining the existing one for the cards you have vaulted, or to refund historical transactions.
- Style: This component can be styled to match the look and feel of your application (like we have done with the dev portal)
- Country Navigation: Payment processors are listed by country
\n

\n","_postman_id":"117ce4fe-9a46-401d-90cb-ef5e52ba9d71","auth":{"type":"basic","basic":{"basicConfig":[{"key":"username","value":"{{session_key}}"}]},"isInherited":true,"source":{"_postman_id":"761f7378-b500-44c8-839b-304826336f93","id":"761f7378-b500-44c8-839b-304826336f93","name":"Shuttle - Legacy","type":"collection"}}},{"name":"20201111","item":[],"id":"388ed4aa-121c-450c-a204-67010b708905","description":"

New Features

Applications now support a default_receipt_format, which allows you to control how receipts are generated for child instances (eg \"APP_NAME-00000001\")
API - PUT instances now supports updating receipt format

Improvements

Checkout - Added routing logic to allow multiple wallets to be configured in a single checkout
Checkout - Now supports \"offline\" payment methods (soon to be launched)
Checkout - The ability to include footer text in the checkout window (for T&Cs see web.footer.text)
Transbank - Now uses Banco Central for CLF -> CLP FX
Checkout.com - Now supports \"Require Account Name\" and \"Require Email\" configuration options for their fraud checks
Internal - Many performance improvements
Internal - This release contains many backend architectural changes
API - refund objects now include a \"manual\" flag to indicate if the refund was performed online or not

Bug Fixes

Paypoint - Fixed an issue with Paypoint not rendering correctly in web checkout
Emails - Fixed card due to expire emails not correctly being sent on the first payment in a recurring contract (enterprise)

Localisation Updates

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n

Field	Note
`web.footer.text`	(default ) If populated it will be included at the bottom of the checkout screen. This supports \"Mark Down\" do you can include links eg \"[Terms & Conditions](https://url) Apply\"
`web.payment_form.button.process_offline`	(default \"Pay via #GATEWAY#\") We have added the ability to support \"Offline\" payment methods, like VEEM which does require any user input but in that case sends the user an email post payment. This string defines the default labelling of this payment option.
`web.payment_form.name.placeholder`	(default \"Name\") The placeholder text on the \"name\" field where a card requires the cardholder name
`setup.add-new-connection.modal.connect.cancel`	(default \"Connection canceled by user.\") Displayed when an OAUTH process is cancelled.

","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"2213fb12-6366-4d82-8f45-d4f7bf05258c","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"55719162-3afd-470d-88f4-02de1ec73ab1","type":"text/javascript","exec":[""]}}],"_postman_id":"388ed4aa-121c-450c-a204-67010b708905"},{"name":"20201026","item":[],"id":"05121370-b1b7-4229-8e6c-a87bec498ebe","description":"

Improvements

Checkout: Creating a signature now not only secures the request but restricts the api key created to only the payment instruction signed for

Bug Fixes

Fixed a web checkout screen rendering issue when overiding the default iFrame behaviour, and forcing checkout to render in an iFrame.

\n","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"4de891e0-c508-4f87-a33a-ad0762a9fc6b","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"7158ff3b-57f4-456a-90bd-441114bc34a8","type":"text/javascript","exec":[""]}}],"_postman_id":"05121370-b1b7-4229-8e6c-a87bec498ebe"},{"name":"20201020","item":[],"id":"d2b109c8-1e84-440a-a40b-d14d9075f41d","description":"

New Features

API

Gateways API now returns currencies supported by each gateway
PUT contract now allows setting the next_payment to \"now\"

Checkout

Added the ability for gateways (and in particular braintree) to specify different client side JS for different payemnt methods
Added support for OFFLINE payment methods to support payment methods thats do not require any UX eg VEEM
Set a numeric keyboard on mobile devices for card/expiry/cvc

Cash Management (enterprise)

Added auditing to deposit_slips, deposit_slip_bags
Deposit slip now support removing from bag

Gateways

Auth.net refunds are now passed a reference ID
Auth.net can now make enable requesting a CVC for tokenised payments
Quickbooks Payments - added support for AVS
Quickbooks Payments - added support to pass an accounts' Quickbooks ID as a \"tag\" (QB-{tag}) so that saved cards are stored under a preexisting quicbooks account.
Gateways now indicate if they require support for PENDING in their FEATURES. Developers should ensure they support webhooks if using these gateways.\n REQUIRE_PAYMENT_PENDING - payment / authorise might return PENDING status \n REQUIRE_REFUND_PENDING - refund might return PENDING status\n REQUIRE_CAPTURE_PENDING - capture might return PENDING status

Bug Fixes

PUT legal_entity_routes - 404 bug resolved
Auth.net now handles duplicate customer payment profiles

\n","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"99f27d39-1319-4723-91b8-86b98e99abaf","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"bb237203-2085-4fdc-97a0-aa1fb5a2771f","type":"text/javascript","exec":[""]}}],"_postman_id":"d2b109c8-1e84-440a-a40b-d14d9075f41d"},{"name":"20210902","item":[],"id":"2b495bed-5623-4040-8ea8-2bb8c27cd318","description":"

New Features

Some gateways allow you to capture more than the authorised amount (eg PayPal), to support this we have added max_capturable to authorisation transactions, you can now capture up to this amount.
Added webhooks for instance management - INSTANCE.CREATED, INSTANCE.UPDATE, INSTANCE.ARCHIVE
Refunds / captures performed through Stripe Dashboard are now reflected in Shuttle

Improvements

Added support for 13 digit VISA cards
During checkout when forcing \"save_card\" for a wallet, changed the behaviour from presenting \"Add Card\" + \"Pay by [Wallet]\", as they are functionally equivalent - only \"Pay by [Wallet]\" will appear
Braintree now validates vaulted cards
When embedding the \"Merchant View\" shuttle will automatically adjust the height of the iFrame
Improved performance when saving a gateway, and refreshing a gateway's access token
Square now recognised the country the merchant is from and adjusts the available functionality (payment while vaulting a card not available in Europe)

Bug Fixes

Fixed an issue with the capabilities API not always reflecting changes immediately
Stripe - fixed an issue where email was not passed correctly for onboarding new accounts
Fixed an IE11 issue during checkout
Fixed deep_link creation error message when an invalid enumeration used
Fixed an issue when reinstating a CANCELLED contracts in which cancel_retries was set to true

\n","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"32ce0ce8-1fb1-4a44-a301-aed9286baff1","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"fbe17062-e1c8-4b77-88ad-ce983b3909e2","type":"text/javascript","exec":[""]}}],"_postman_id":"2b495bed-5623-4040-8ea8-2bb8c27cd318"},{"name":"20210824","item":[],"id":"a112f222-9417-40e3-96ee-66d2d217eaa1","description":"

Improvements

Merchant View

The merchant view now supports window events DASHBOARD_DISPLAY, DASHBOARD_ERROR, SESSION_EXTEND

Bug Fixes

Merchant View

Various UX bug fixes
Better support for international phone numbers

Onboarding

Fixed component height when a modal popup is bigger than the underlying page

Localisation

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n

Code	Label
`dashboard.general.buttons.download`	download
`dashboard.general.buttons.upload`	upload
`dashboard.general.buttons.remove`	remove
`dashboard.general.input.upload.size-error`	The maximum file size allowed is 16kb
`processing.general.buttons.download`	download
`processing.general.buttons.upload`	upload
`processing.general.buttons.remove`	remove
`processing.general.input.upload.size-error`	The maximum file size allowed is 16kb

","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"bff09db5-8247-43a1-b27f-a16adfea351f","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"a6acdd0f-ac6b-4c9a-87eb-f35b28d58e25","type":"text/javascript","exec":[""]}}],"_postman_id":"a112f222-9417-40e3-96ee-66d2d217eaa1"},{"name":"20210722","item":[],"id":"5e85dcb7-7d51-4f44-af8c-5a603c6794d5","description":"

New functionality

Authenticate: You can now use Shuttle for a customer to login via PayPal and collect shipping address during checkout (see Deep Links > Authenticate)

Improvements

API

Instance API now supports instance_key field
Gateways API now supports:
- features: Identify which features the gateway supports
- checkout_js: Javascript that must be injected at checkout
- authenticate_js: Javascript that must be injected at authenticate\n The API also supports expand both checkout_js and `authenticate_js
\n
Some APIs did not apply a default order, this now defaults to \"created:asc\"

Go Cardless

Now payments updates appear on the transaction object rather than just the audit history, triggering PAYMENT.UPDATE webhook. Gocardless webhooks are also captured in the gateway_metadata

Braintree

Resolved issue \"Cannot read property 'email' of undefined\"

Stripe

Resolved stripe refunds showing up as a negative in the settlement amount

PayPoint

Added additional logging due to Paypoint occasional unavailability error

Checkout

AVS mandatory fields updates to address line 1, city, postcode.

Onboarding

Countries now ordered alphabetically
Widget height calculation now takes into account popups
Fixed an issue with subfield checkbox rendering (GoCardless)

Portal

You can now update your own details
Added internationalisation to number formatting

\n","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"121f2d71-8680-471f-8807-7eb15180a5f3","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"462233dd-a477-4bce-b2c5-c2c1e2747951","type":"text/javascript","exec":[""]}}],"_postman_id":"5e85dcb7-7d51-4f44-af8c-5a603c6794d5"},{"name":"20210608","item":[],"id":"403b9f95-4b73-4584-9832-319923e34910","description":"

API

New Features

You can now fetch and update gateway configuration via the /gateway/:id/settings API
(enterprise) New communication APIs available to access system emails

Improvements

transaction objects now return voided and authorised (amount - captured - voided) where appropriate
Sessions now return ip_address_currency and ip_address_country
You can now query payment_methods by merchant, you no longer need to specify an account
Where possible we will no longer return fields which are not used, such as split if split payments are not used

Onboarding

New Features

You can filter the list of gateways available during onboarding on a case by case basis, via processor_filter field. This allows you to streamline connecting a specific payment processor

Improvements

When only a single payment processor available, the merchant is no longer presented the processor selection page
When a session expires the screen transitions to a session expired page, rather than failing on next interaction

Bug Fixes

Fixed an issue where in some cases the UX would be vertically cropped

Checkout

Improvements

Checkout has been enhanced to better support VEEM
You can now pass default_occurrences to checkout to allow this field to be editable pre-populated with the default
You can now pass \"false\" for default_occurrences and default_start_date to allow these fields to be default deselected but edited by the user
Changes the UX flow where the amount is editable however the configured gateway needs to know the amount in their embedded library

Admin Portal

Improvements

You can now see your organisation id
Removed the legacy gateway setup buttons
When a session expires the screen transitions to a session expired page, rather than failing on next interaction

Bug Fixes

Fixed the % change calculation when looking at month on month growth
Fixed an issue where localisation editor would sometimes be displayed when disabled
Fixed some UX display issues

Stripe

Fixed an issue for merchants with with non utf8 content in their company name

Worldpay

Transactions are now populated with metadata containing the API requests used to communicate with Worldpay

Transbank

The Transbank integration has been upgraded to the new REST integration
The Transbank SOAP integration has been deprecated and is no longer available for new connections.

PayPal Commerce

Now available!
The Paypal Business integration has been deprecated and is no longer available for new connections.

\n","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"ae0bc969-24c4-4823-a3d8-f0f3607f0e97","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"52272ad0-95cb-4760-9583-7beedde40e70","type":"text/javascript","exec":[""]}}],"_postman_id":"403b9f95-4b73-4584-9832-319923e34910"},{"name":"20210601","item":[],"id":"66836abc-2dd1-4e45-9427-524af0da5b20","description":"

New Features

Recurring payment cancel API now supports cancel_retries if you want to run your own dunning process

Improvements

Select box placeholders are now localised
You can now instruct a payment via a gateway token without specifying the gateway_id
Various optimisations to provide better audit trails on objects
Portal now supports account lockout due to too many login attempts
Support for REDCOMPRA payment method

\n","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"25b15d19-af2b-4b34-a56d-164d82402abf","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"91340a27-d2da-4aaf-a291-62b230546336","type":"text/javascript","exec":[""]}}],"_postman_id":"66836abc-2dd1-4e45-9427-524af0da5b20"},{"name":"20210521","item":[],"id":"b667c183-380a-40ec-b3c1-0b856757c780","description":"

New Features

You can now pass in the gateway token when instructing an API payment

Improvements

Refunds will now trigger PAYMENT.UPDATE webhook on the source transaction
The account API no longer requires \"CRM-\" prefix when requesting account using the crm_key
Transaction API now includes the processor for the transaction
GoCardless payment button now supports new localised text when the currency is editable
Posting comments into the API now supports CORS

Bug fixes

Nonce support works with both one off payments and recurring payments
Hosted payment popup no longer reports an error when a transaction is unresolved

\n","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"fe178f97-8383-489d-9cd0-3373e5f2860e","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"1829b1c8-f1fd-41c1-a157-d471886cba15","type":"text/javascript","exec":[""]}}],"_postman_id":"b667c183-380a-40ec-b3c1-0b856757c780"},{"name":"20210428","item":[],"id":"7672d4ae-f009-4380-ade4-05bd7fc3b726","description":"

This release is an update to the \"Merchant View\".

New Features

Added manually capture / void to the transaction screen of an authorisation
Added the ability to download attachments from comments

Improvements

Improved the display when configuring multiple languages, to reflect all the languages configures for the app/organisation
Improved the display of refunds which were notified by the gateway but did not happen through Shuttle
Streamlined the transaction timeline / audit history display
General UX improvements
(enterprise) General improvements around Gift Aid, emails and other components

Bug fixes

Added ordering to the audit history
Fixed a UX issue when manually resolving a transaction
Fixed a bug whereby the first comment on an object would sometimes be lost
Fixed an issue where some users with badly configured proxies would see an encoding error

Localisation Updates

\n\n\n\n\n\n\n\n\n\n\n\n\n

Field	Note
`general.statuses.notification-received`	(default \"notification received from gateway\") When a transaction event was not initiated from Shuttle but from the gateway

","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"e28a6c2b-ba10-4993-b483-7a9453ddd72e","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"5a08acb2-5dc8-4d5e-8187-31b790bbfe86","type":"text/javascript","exec":[""]}}],"_postman_id":"7672d4ae-f009-4380-ade4-05bd7fc3b726"},{"name":"20210319","item":[],"id":"0d27dc28-dec2-4261-8e0b-bf68d35170ee","description":"

New Features

Merchant View

The merchant view has had a major overhaul
Styling simplified to feel more natural embedded within your application
Deep links allow you to customise styling, using the same theme as onboarding
Added the ability to make notes against all items in the merchant view so that you can keep track of any payment related issues / activities
Added the ability to see a more detailed audit history for all objects to help you better understand what has happened and when
Merchant view now allows manual capture / void of authorisations
You can now edit the amount of a recurring contract
You can now refund unattributed transactions

shuttle.js 1.2.x

The javascript library 1.2 branch has been released
Added the ability to inline embed onboarding and merchant view in a div
Replaced \"bindButtons()\" with bind()\" to better reflect non button binding
Renamed from payments.js to shuttle.js, and simplified the URL

\n","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"87a8e4b6-a553-4a40-b2dd-2b011c5a9f55","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"6acc78ce-fad9-4f51-bfd2-648c5f21e150","type":"text/javascript","exec":[""]}}],"_postman_id":"0d27dc28-dec2-4261-8e0b-bf68d35170ee"},{"name":"20210222","item":[],"id":"d6203710-4117-4e25-a3ed-d0c8225a86b2","description":"

New Features

API

You can now cancel a next payment attempt on a contract in arrears but passing a blank next_payment date
Transaction objects of type REFUND now return a link to the refund object
Transaction objects of type AUTH now return a field expires when the authorisation expiry date is known
A gateway object now has a status_reason
which may provide further information as to the gateway status. Square populate this when revoking Shuttle's access to an account from the Square dashboard
Instance creation now allows unnamed instances
Added the ability to log out via DELETE /sessions
Added the ability to reattribute a transaction via API POST /transactions/:id/reattribute

Recurring

You can now pass an optional write_off flag when cancelling a recurring payment, if you want to write off the amount in arrears. If the contract is in arrears andf you do not pass this it will go to a CANCELLING status until the arrears paid.
You can now \"resume\" a CANCELLED / CANCELLING contract by passing the resume flag
You can now pass a contract to a payment popup, if you want to pay the amount towards the contract if is in arrears
Extended the nonce functionality to prevent duplicate contracts being created even if no initial transaction
Now when updating a contact's next_charge or next_payment to now, they are run within seconds rather than minutes
When attaching a new payment_method to a contract, if there is an outstanding amount on the contract a payment will be attempted immediately (asynchronously)

Bug Fixes

Fixed an scenario where a recurring payment with a future start date would be created if the card tokenisation failed
Fixed an issue where in some cases a payment requiring 3DS would create a second transaction for payment completion
Fixed a out of bounds error on some split payments
When instructing a payment with person details, if the person already exists in Shuttle their details are updated, however a person's tags were not being updated
Fixed an issue where attaching an new payment_method to a failing contract that was not in arrears would not revert the contract to ACTIVE
Cleaned up GoCardless checkout button label
Fixed a card checkout issue where chrome auto fill sometimes would not automatically enable the \"Next\" button
Fixed modal overlays which would link to \"#\" if the user clicked \"Show Me\"
Fixed an issue preventing a custom receipt format being saved to new instances on creation
Sage Pay renamed to Opayo

Localisation Updates

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n

Field	Note
`web.payment_form.error.invalid.contract.account`	(default \"Account doesn't match contract\") When paying the arrears on a contract, presented if the contract does not belong to the user passed
`web.error.gateway_start_payment_issue`	(default \"Payment cannot be performed at this time (#REASON#)\") Some processors require we inject their code at checkout, this message is presented if there is an issue doing this.
`web.payment_form.payment.cancelled`	(default \"Payment cancelled\") Displayed if a payment is cancelled
`web.payment_form.button.change_amount`	(default \"change amount\") Displayed when a variable amount allowed on the UX, but if a gateway needs a fixed amount amount entry and card details will split into a 2 step process
`setup.processors.oauth.popup.dismiss\"`	(default \"Cancel\") Displayed on some OAUTH processes
`setup.processors.onboarding.cancelled`	(default \"Cancelled\") Displayed if a onboarding is cancelled
`setup.processors.onboarding.error`	(default \"Invalid response from onboarding.js\") Displayed if a onboarding error is encountered from gateways requiring JS injection
`setup.processors.onboarding.missing`	(default \"Missing onboarding.js file for #PROCESSOR#\") Displayed if a onboarding error is encountered from gateways requiring JS injection

","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"7a6dd4c3-baac-43d2-bbfa-cc15c5cddd09","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"2ff57b95-ebf5-4ca5-b8fd-c1db94e82dc6","type":"text/javascript","exec":[""]}}],"_postman_id":"d6203710-4117-4e25-a3ed-d0c8225a86b2"},{"name":"20211213","item":[],"id":"853b599b-4481-452b-8160-65991c39233c","description":"

Bug Fixes

Fixed an issue with some recurring payments not dunning correctly (retry policy)

\n","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"02420b94-55ab-442a-8a7a-b83af868ed74","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"2ad3797b-b287-4b80-9aa9-911ba42e1377","type":"text/javascript","exec":[""]}}],"_postman_id":"853b599b-4481-452b-8160-65991c39233c"},{"name":"20211206","item":[],"id":"1df450d7-1a83-49b5-a7b7-6678cb6df3d9","description":"

New Features

You can now filter gateway availability to ones that support AUTH (if you need auth/capture), SAVE_CARD (if you need vaulting), or exclude those requiring javascript injection (if you've built your own checkout that doesn't support this)
Trust Payments integration now available

Improvements

GoCardless will mark a payment as success on CONFIRMED rather than SETTLED
When disabling a save_card feature it will no longer be rendered
Merchant view now supports cookies disabled
(enterprise) role permission editor now hides archived teams
(enterprise) new platform wide role permissions (see enterprise notes)
Payment methods lists out any recurring payments using that method
VOID events now display in the merchant view

Bug Fixes

Shipping address not passed to some gateways when paying with a saved card
Merchant view transaction audit not displaying

\n","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"d9260b28-735c-4d04-bb48-bacd511bbf52","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"56359615-6c16-41a6-ad5b-56510f57a703","type":"text/javascript","exec":[""]}}],"_postman_id":"1df450d7-1a83-49b5-a7b7-6678cb6df3d9"},{"name":"20211123","item":[],"id":"f2d7425e-50b9-4c39-84b6-e6828a6aac89","description":"

New Features

API ability to restrict processors to those that support AUTH, SAVE_CARD, or exclude ones that require JSWRAPPER
Added checkout parameter force_add to disable presenting saved cards on an account

Improvements

Changed legal_entity_routes to have consistent behaviour between single entity and multi entity instances
Instances now returns date of last_transaction, last_contract, and also the non ARCHIVED processors
CONTRACT.UPDATE now sent when updating the number of occurrences
Improvements around contract retry date calculations, and retry complete, especially when it comes to manual payment attempts
Added AVS support to PayPal Flow Pro

Bug Fixes

Fixed an issue where you couldn't select a saved card that was declined (and in a FAILING status) for a new contract
Account edit was producing two saves / UPDATEs
We now prevent a transaction previously marked as declined can be updated as success if the outstanding balance has been cleared
Fixed an API issue with \"expand\" not always working consistently

\n","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"1adf3413-c257-4119-8869-d8379b2c29ab","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"bb9ec74f-cd64-4839-beaf-af46beac9243","type":"text/javascript","exec":[""]}}],"_postman_id":"f2d7425e-50b9-4c39-84b6-e6828a6aac89"},{"name":"20211027","item":[],"id":"c28dc7bb-f1c5-4f3b-ab94-21853f6bc8ac","description":"

New Features

You can use Shuttle in on-prem/installed scenarios (eg installing on wordpress or salesforce). You can now create a secret_key for an instance, then authenticate against the API using that
You can now pass level 3 payment processing data (line_items) at checkout and these will be passed to supported gateways
You can now update the number of occurrences on a recurring payment

Improvements

Recurring payments with a start date in the future, where you're tokenising a new card at the same time now better supports SCA to improve approval rate
\n
SCA transaction data is now available in the API
\n
Several performance improvements including saving a gateway
\n
Gateways that dont support multi_capture no longer report a remaining authorised amount after a partial capture
\n
Refunding a CAPTURE will now indicate the refund on the original AUTHORISATION in addition to on the capture, as such it will fire PAYMENT.UPDATE and CAPTURE.UPDATE webhooks.
\n
Additional information on the API
\n
- instance - secret_key
- capture - balance, currency, refunded
- contract - retry_complete
- payment_method: advanced_notice_hours, failing_reason, failing_since, mandate_id, requires_cvc
- transaction - currency, browser_ip_address, browser_accept_header, browser_javascript, browser_locale, browser_user_agent, browser_size, browser_java_enabled, browser_color_depth, browser_timezone
- session - permissions
\n
Fixed an billing issue with the last day of the month's transactions not being billed
\n
checkout now supports CHECKOUT_DISPLAY browser events
\n

Bug Fixes

Added some missing MAESTRO number ranges
Fixed some localisation editor bugs
Removed user_offline flag from webhooks

\n","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"81ca91c5-13a0-4458-896d-b4303368c536","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"f662fac7-332f-4f7b-8c33-6b08751e01fa","type":"text/javascript","exec":[""]}}],"_postman_id":"c28dc7bb-f1c5-4f3b-ab94-21853f6bc8ac"},{"name":"20211006","item":[],"id":"ee56559e-cf28-4aef-b39b-101ce419be71","description":"

Improvements

Checkout hosted processes during checkout now are dynamically sized to best suit the process
Checkout address verification load speed has been improved
Checkout now filter to support only ACH / SEPA / CARDS via the payment_method_types option
Cancelling a contract with \"cancel_retries: true\" will not attempt to collect the outstanding amount
If a automated recurring payment returns a 3DS challenge, this is now treated as a decline
Spaces are no longer allowed in crm_key
Reset password emails better handle expiration

Bug Fixes

Starting account edit was creating a new object version
Could not adjust \"next_payment\" attempt for a recurring payment when on the last occurrence
3D Secure display has been improved

\n","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"d7131880-9ee5-4677-853f-eebee1102322","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"3f3c1322-b902-4f43-87d6-79be773a8bd2","type":"text/javascript","exec":[""]}}],"_postman_id":"ee56559e-cf28-4aef-b39b-101ce419be71"},{"name":"20220117","item":[],"id":"e1a5e7ec-170e-4b9c-8d66-67d50c69a01b","description":"

New Features

Chargebacks, we've added early support for reporting chargebacks, initially on Stripe, Checkout.com and Paypal
Private beta of instance specific webhooks and api_keys (designed for platforms installed on client infrastructure eg Salesforce.com or magento instance)
Stripe now supports ACH, SEPA, Multibanco

Improvements

Added support for hosted authentication processes
Added support for line item data in hosted checkout processes
Application list performance
Trust payments 3DS process now works better when style: INLINE
(enterprise) Improved report performance

Bug Fixes

Checkout.com fixed an issue handling checkout.com webhooks
Instance search was case sensitive in some areas, it should not be
Fixed an issue with trimming long values for state on Opayo

\n","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"9edb0f83-eb0f-41bf-9f97-be1351912c1c","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"ca186ff7-3b1c-4102-bc6d-2d7c617cbed5","type":"text/javascript","exec":[""]}}],"_postman_id":"e1a5e7ec-170e-4b9c-8d66-67d50c69a01b"},{"name":"20201126","item":[],"id":"8c8a6922-ad4e-4841-bbe8-210b9eb7d616","description":"

New Features

API

Contract refunds are now available, refund multiple transactions in a single request

\n","event":[{"listen":"prerequest","script":{"id":"53ee5605-3018-470d-a03a-6e896f3d9266","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"e511fa70-0451-446c-9a59-5c81537e9d0e","type":"text/javascript","exec":[""]}}],"_postman_id":"8c8a6922-ad4e-4841-bbe8-210b9eb7d616","auth":{"type":"basic","basic":{"basicConfig":[{"key":"username","value":"{{session_key}}"}]},"isInherited":true,"source":{"_postman_id":"761f7378-b500-44c8-839b-304826336f93","id":"761f7378-b500-44c8-839b-304826336f93","name":"Shuttle - Legacy","type":"collection"}}},{"name":"20220206","item":[],"id":"843c8dc1-0355-425d-a585-d0a501cd032d","description":"

New Features

Support for \"scheduled payments\", applications that need to schedule payment for some point in the future can now do so with scheduled_date and scheduled_days.

Improvements

General configuration performance improvements
Web checkout now supports hiding the \"save_card\" button without affecting its functionality via hosted_save_card
Webhooks raised for recurring payments have been simplified
The stripe customer object is now better populated for Stripe payments

Bug Fixes

Fixed an issue with some Braintree card expiry dates not being reported correctly
Fixed an issue with Venmo QR codes being cropped on Paypal Commerce
Fixed an issue with \"hosted add payment method\" displaying for disabled payment methods

Localisation

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n


error.validation.scheduled_payment.auth	Scheduled payments do not support auth / capture
error.validation.scheduled_payment.save_card	Scheduled payments do not support `save_card: false`
error.validation.scheduled_payment.frequency	Scheduled payments do not support frequency
error.validation.scheduled_payment.date	Scheduled payments must be scheduled for at least 1 minute in the future

","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"7aea5813-ea39-44f6-a1b9-a6fe4e9cc344","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"c65f62f7-05ed-4a8d-90d5-bd95f88dfdc1","type":"text/javascript","exec":[""]}}],"_postman_id":"843c8dc1-0355-425d-a585-d0a501cd032d"},{"name":"20220816","item":[],"id":"f4d90fb6-3b24-4482-a24d-d7c5ee00c519","description":"

New Features

Added PAYMENT.UNRESOLVED webhook so you can now automated actions based on this event

Improvements

More efficient handling of multiple connections to the same Stripe account
GoCardless connectivity errors (502) now mapped to DECLINE_RETRY
More informative error messages when handling errors during checkout from gateway javascript libraries (eg NMI 3DS issues)
Improved error handling for webhooks

Bug Fixes

Fixed an issue causing payment methods to temporarily \"disappear\" for Paypal Commerce during credential refresh

New Features

We've added support for Twilio Pay to support clients that require telephone / IVR payments, please contact our support if you wish to use this

Improvements

Email addresses passed into the API are now trimmed of leading / trailing spaces to accommodate platforms with lax input validation
Removed functionality that moved a payment method that had been failing for 3 months to a FAILED status, these will remain in FAILING and can continue to be retried.
Scheduled payments that fail due to an technical / configuration error (DECLINE_ERROR) will now be retried in line with a temporary issue schedule (ie minutes) rather than a bank decline retry schedule (days)
Improved the meta data sent to GoCardless on mandates and payments to me more useful
Relabelled gateway timeouts errors to be more helpful

New Features

Private integrations - you can now provision gateways on an account by account basis
Share the URLs you are hosting checkout to enable Paypal Fraud Net and soon Apple Pay

Improvements

Onboarding now connects to the payments marketplace for merchants looking for a new processor
Tokenising a payment method via API no longer requires you to specify which gateway you want to use
NMI now supports 3DS, and ACH
Auth.NET now supports level 2 data
API keys now display in a predictable order
Added \"account\" to the refund, charge and void objects
List item APIs now support a between operator, for example searching between a date range

Improvements

Paypal now passes alt_key as invoice_id
Paypal now allows optional cancelling of billing agreements after use, to prevent the customer getting an email
checkout.com now passes alt_key in token payments
Authorize.net now adds email address to customer profiles

Bug Fixes

Opayo rejecting certain colour depths during 3ds
Opayo rejecting invalid email addresses
Paypal rejecting invalid shipping addresses
Paypal rejecting line items with no tax specified
Sandbox tokenise not correctly saving cards

New Features

You can now embed credit terms for BNPL providers on your webpage (requires shuttle.js 1.3.0+)
You can now post new instances without a secret key for on-prem installs (requires manual activation)

Improvements

You can now change a payment method to \"saved cards only\" rather than fully disabling
Merchant view: Improved how declined transactions render
Performance improvements
Added support for signature creation for payloads with non latin1 characters
GoCardless now supports mandate replacement webhooks
GoCardless now schedules payment instructions by 4pm to meet daily cutoffs
Transactions which are waiting for 3DS to completed now return the 3DS url in the object (up to 15 minutes after requested)

Bug Fixes

Contracts don't transition to complete when the final payment is PENDING until the transaction resolved

New Features

Stripe now supports ACH + SEPA
Affirm Buy Now Pay Later provider now available

Improvements

You can now maintain multiple Shuttle connections to the same gateway account
Future payments can now be up to 365 days in the future (previously 31 days)
PayTomorrow now includes a monthly price estimator at checkout
Authotise.NET now supports pending (held) payments
Checkout.com now performs payment as AUTH -> CAPTURE to better handle 3DS failure scenarios
Various improvements to Paypal Commerce integration

Bug Fixes

Opayo name fields now trimmed to max lengths

New Features

The merchant view now displays scheduled payments in the \"Scheduler\" section
The user can now edit the payment method on a scheduled payment
The onboarding module now uses websockets for a live view of what's configured, providing a better experience where there's more than one user

Improvements

API transaction now has \"resolved\" date of when manually resolved
Updated a hosted checkout process from presenting a TOKENISATION link when PAYMENT_AND_TOKENISATION available and requested for a more streamlined experience
Merchant view advanced transaction search now allows filtering on action (\"PAYMENT\" / \"AUTH\" / \"REFUND\" etc)
Saved payment methods are now filtered to only those that support the operation (for example, saved ACH details wont be presented when the user is doing an AUTH)
The \"capture\" screen now defaults the \"whole\" amount to the \"authorised amount\", not the \"max capturable\" amount (when these are different)
NMI now validates webhooks are configured correctly during setup
The onboarding module now displays INACTIVE gateways that have saved cards stored on them and enabled as \"SAVED CARDS\", so its more clear these are still used for saved paymet methods
Square now support MOTO and MIT (note, MOTO tokenisation not supported by Square)
Square now supports ACH
Square now passes line item detail to the gateway where available
Paypal now passes line item detail to the gateway where available
Paypal now supports the vaulting API (note, MOTO tokenisation not supported by Paypal)

Bug Fixes

Creating a child contract now gracefully handles a client sending multiple concurrent requests
A transaction max_capturable amount is now limited to 4 decimal places
Save checkbox broke in some scenarios toggling back and forward between cards and ACH
Fixed an issue where card ending and expiry was not always displaying correctly on Paypal

\n","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"93ad542e-253f-4b57-a38d-192dc9e19083","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"8a41ac64-8077-48f2-9429-658883c4093d","type":"text/javascript","exec":[""]}}],"_postman_id":"4cf72d74-7df1-4061-b491-26bae9a97502"}],"id":"2ed853fc-5d74-48bb-a5da-884596529e2d","_postman_id":"2ed853fc-5d74-48bb-a5da-884596529e2d","description":"","auth":{"type":"basic","basic":{"basicConfig":[{"key":"username","value":"{{session_key}}"}]},"isInherited":true,"source":{"_postman_id":"761f7378-b500-44c8-839b-304826336f93","id":"761f7378-b500-44c8-839b-304826336f93","name":"Shuttle - Legacy","type":"collection"}}}],"auth":{"type":"basic","basic":{"basicConfig":[{"key":"username","value":"{{session_key}}"}]}},"event":[{"listen":"prerequest","script":{"id":"011a0940-7861-456b-b341-23c4344050b3","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"3a630545-2c02-4e1b-928c-383dac891fec","type":"text/javascript","exec":[""]}}]}