After you have finished configuring your site and have tested thoroughly, follow the final steps below to begin processing live payments.
Before you continue…
Most acquiring banks mandate that 3-D Secure is performed prior to AUTH requests.
If 3-D Secure is not implemented, you could be liable for fines from the card schemes.
Ensure you have contacted your acquiring bank and have configured 3-D Secure, if required.
You must ensure your servers are PCI compliant before processing live payments.
For further information, we recommend contacting your acquiring bank.
You must read and ensure you have understood the practices outlined in our "Checks to perform following payment".
You must perform a full suite of test payments using all 3-D Secure v2 and 3-D Secure v1 cards provided on this page and ensure your system handles each scenario correctly and displays the correct message to the customer. Click here to open this in a new tab.
You must ensure your system can submit requests using your test sitereference (starts with “test_”) and handle both successful and failure responses before processing live payments.
Rules for live site reference
When you are ready to switch your account live, you will need to consider any Rules that may have been configured on your test Site Reference, as these will need to be re-configured on your live site reference to ensure they update your system as expected. Click here for our Rule documentation.
Get in touch
Once you have tested your system and received email confirmation that your account is ready to go live, contact our Support Team with your live site reference and request to go live. You will receive a response when your live site reference is ready to begin processing payments.
Only the authorised contact for the account can request for the site reference to go live.
Make changes to your requests
You will need to make the following changes to your requests to Trust Payments:
- You will need to update your requests so your live site reference is submitted in the sitereference field in the JWT payload. Once this change has been made, requests will be processed as live requests.
- You will need to ensure your instance is configured in the production environment, rather than staging.
TrustPayments.instance.configure(username: username_from_trustpayments,
gateway: .eu,
environment: .production,
translationsForOverride: nil
)
Live testing
Once you have contacted our Support Team to enable your live site reference and made the necessary changes to your requests as described above, we recommend processing a test payment in the production environment using a live card by using Apple’s promo codes. This is to ensure the payment is processed successfully and your app behaves as expected before making the latest release of your app available to customers.
This process cannot be completed using TestFlight. This is because the payment SDK will not initialise from a non-trusted source. The only trusted source is the Apple App Store.
You should not use the same live card too many times, as the requests may still be authorised, and could cause the issuer to suspect fraud or the cardholder could exceed their limit.
When creating a new release of your app and this has undergone review and is awaiting manual intervention to be published to the App Store, you can download the app using a promo code and then perform a live payment. Once you have tested the app to your satisfaction, you can then manually push the app to the App Store.
When creating a new release version of the app, you will be asked whether or not you want the app to be released automatically following the app review performed by Apple. Ensure you decline, by selecting the option to release the version manually.
After testing, you can cancel processed transactions using Portal.
You’re all set!
Remember to sign in to Portal and to check your transactions regularly to ensure payments are being processed successfully. If you need assistance, please contact our Support Team.
