Payments

use the payment object to request and record payments payment records contain all the information needed to control the payee experience via the paypage, including currencies, payment routes available, amounts, and languages payment records also direct users to different pages depending on if the payment was successful or failed these records can be pre populated with as much or as little information as you choose, and can be created either manually or automated since version 2 17, payments are immediately processed in older releases, payments will be processed through daily batches after creating their records inbound payments the inbound payments feature enables businesses to manage and automate the collection of customer payments directly within salesforce how it works create a payment record a payment record is generated, specifying the type (in this case, inbound), amount, due date, payment route, and associated authorisation payment records support multiple payment methods, including card payments, direct debit payments, ach/echeck, and paypal payment processing & collection once submitted for collection, the payment request has been sent to your payment gateway to attempt collecting funds from the customer a payment record submitted for collection should not be changed as it is awaiting a response from the psp as such, the actual status of the payment depends on the payment gateway's processing once a payment record has been processed, all the relevant information from the psp is populated on this record alongside a status update details such as the payee name, time and date of payments, any error codes, transaction references, etc are all visible on the payment record outcome payment records are updated with the transaction status, allowing businesses to track successful and failed payments if the collection is successful, the payment updates to collected from customer if it fails, the system retries until success or until all attempts are exhausted (resulting in a failed status) you can also cancel the payment, which moves it to cancelled flowchart graph td a\["payment created in unaric payments (awaiting submission)"] > b\["submitted for collection"]; b > c{payment collection successful?}; c yes > d\["collected from customer"]; c no > e\["retry in progress"]; e > f\["payment resubmitted (gocardless settings)"]; f > g{payment collection successful?}; g yes > d; g no > h{retry attempts exhausted?}; h yes > i\["failed"]; h no > e; b > l\["submit payment for cancellation"]; l > j\["pending for cancellation"]; j > k\["cancelled"]; classdef startend fill #002d4c,stroke\ none,color #fff,font weight 400,font family\ helvetica,rx 5px,ry 5px; classdef process fill #42a4dd,stroke\ none,color #fff,font weight 400,font family\ helvetica,rx 5px,ry 5px; classdef decision fill #f4f7fa,stroke\ none,color #002d4c,font weight 400,font family\ helvetica,rx 5px,ry 5px; class a,d,i,k startend; class b,e,f,j process; class c,g,h decision; key fields fields description payment route options (required) allows you to choose which payment routes are available to your customer to use e g card, direct debit or ach amount (required) the payment amount currency the payment currency required if multi currency payments are enabled for the salesforce org ecom url this is the link you provide to your customers to enable them to process the payment status tells you if the payment is awaiting submission, if it's successfully processed, or if it failed for some reason status description a descriptive text showing the reason related to the current status might contain the reason for cancellation or failure for example when creating a payment from an authorisation, the authorisation field will automatically be populated with the correct record id statuses status description awaiting submission the payment has not yet been processed or submitted to your payment service provider submitted for collection the payment has been submitted to your payment service provider, but the outcome of this transaction is not yet known this is used for direct debit payments, which take a few days to clear collected from customer the payment has been collected from the customer and has been confirmed retry in progress the payment collection attempt has failed and will be retried in a few days this status only applies to integrations with gocardless success+ failed the payment failed to collect the status description field will provide a description of the error if a payment attached to an authorisation fails, the authorisation status will be unaffected the failure of a payment does not necessarily imply a failure of the underlying authorisation (for example, it could simply be that there are insufficient funds in the account at this time ) pending for cancellation this is an intermediate status when submitting a payment for cancellation from salesforce cancellation of payments is currently only supported for gocardless payments cancelled this status suggests that the payment collection was cancelled payments cancellation is currently only supported for gocardless payments payment error codes unaric payments enforces unique codes for each type of error, covering all payment failure cases in this way, it is possible to automate flows that respond to specific failure codes the sanitised responses are listed here code description not completed the payment gateway authorisation screen was not completed correctly declined transaction declined, a reason was not given please try again if no luck, try a different payment method declined auth not found a repeat payment was attempted using an authorisation, but the gateway did not have a record of this authorisation declined name transaction declined, a valid name was not provided declined fraud transaction declined a reason was not given declined avs declined, billing address does not match the address held by the bank please check the address entered declined avs missing info declined, required billing information not specified please check you have completed all required fields declined aba declined, routing number was incorrect declined card details declined, card details were incorrect please check the card details entered if the problem persists please contact your card issuer or try a different payment method declined mandate error the mandate has failed, was canceled, or has expired declined duplicate declined, duplicate transaction please do not try again as payment has most likely already been collected please contact the company you are trying to make payment to declined cv2 declined, card security code was incorrect please check the last 3 digits on the reverse of the card and try again declined issue invalid issue number please check and try again if the problem persists please contact your card issuer declined start date declined because the start date is in the future please enter a start date that is in the past declined expiry date declined, card expired please use a different card or contact your bank declined invalid amount declined, invalid amount please check the amount and try again if the problem persists, please contact the company you are trying to make payment to declined invalid email declined, the email address is mandatory and a valid one was not provided please try again and enter your email address declined unsupported card type declined, the card you used isn't supported please try with a different card or contact the company you are trying to make payment to declined wrong card type declined, the card type you specified does not match the card number please check the card details entered declined unsupported currency type declined, the currency you used isn't supported declined unsupported currency type asp declined, no payment service provider has been set up for this currency declined amount too large declined, the amount is too large declined insufficient funds declined, there are insufficient funds on this account declined payer deceased declined, this account belongs to someone who is deceased declined gateway error declined, the gateway encountered an error please try again in a few minutes if the problem persists, please contact the company you are trying to make payment to raw psp response messages aside from error codes, unaric payments passes through the raw response messages from the connected psp this provides further detail in understanding the outcome of payments and authorisations to enable this feature navigate to setup > object manager select the object for which you want to enable these response messages go to the page layouts tab and select the page layout to modify add the raw error message from psp field