PSP Passthrough Parameters

psp passthrough parameters allows you to send specific data to your psp on authorisation and payment records this data can include references for accounting or auditing purposes additional fields required by certain organizations (e g , financial institution data) internal payment descriptions any other information your psp requires currently, unaric payments offers passthrough parameters for gocardless and sagepay for support with additional psps, contact https //support\@asperato com how it works data transmission occurs for both repeat and web based transactions the data must be entered as a syntactically valid json object containing key value pairs, which makes it unsuitable for manual use instead, a process should be used that collects the required data on a separate screen, formats the data appropriately, and inserts it into the field the data set on the field is psp specific this means if you switch to another psp, and populate the same data on the field, it may not be passed to the new psp in the same way to use this feature, enter the data in the psp passthrough parameters field on the payment or authorization record in salesforce this field accepts data in json format, which organizes information as key value pairs (e g , {"key1" "value1", "key2" "value2"}) the field isn't visible on the default layout for either payments or authorisations, so must be added manually to view it development work is involved in implementing this feature we strongly suggest appointing a salesforce consultant to manage implementation the psp passthrough parameters feature is supported by unaric payments from versions from 2 13 onwards gocardless gocardless supported fields key "description" set a custom description for payment records using the description key this appears in customer notification emails and on the gocardless dashboard example {"description" "test description"} key "reference" used for adding a reference to payment records (appears on customer bank statements) example {"reference" "testref"} test custom references thoroughly in a sandbox before live use gocardless must enable this feature, and format requirements vary by payment scheme incorrect formats can cause transaction failures keys "payment metadata", "customer metadata", "mandate metadata" used for sending custom key value pairs for payments, customers, and mandates gocardless currently limits to three key value pairs per metadata type add description to payment records gocardless allows you to include a description for payment records, providing additional context for transactions this description is sent using the "description" key within the psp passthrough parameters field please note that descriptions are only supported for payment records and cannot be used for mandates when gocardless sends notification emails to your customers, this description will be included additionally, the description is visible on the payment record within the gocardless dashboard by default, unaric payments automatically adds its transaction reference to the description field in gocardless if you specify a custom description using the psp passthrough parameters, the unaric payments transaction reference will be replaced to add a custom description to a gocardless payment record navigate to the payment record in salesforce locate the psp passthrough parameters field (if this field is not visible, ask your salesforce administrator to add it to the page layout ) enter the description in json format using the "description" key {"description" "your custom description here"} save the payment record add payment references gocardless allows you to include a reference for payment records, providing a unique identifier that appears on your customer's bank statement this reference is sent using the "reference" key within the psp passthrough parameters field please note that references are only supported for payment records and cannot be used for mandates to add a custom reference to a gocardless payment record navigate to the payment record in salesforce locate the psp passthrough parameters field (if this field is not visible, ask your salesforce administrator to add it to the page layout ) enter the reference in json format using the "reference" key {"reference" "yourreferencehere"} save the payment record send custom metadata gocardless allows you to send custom key value metadata pairs for customer, payment, and mandate records this metadata provides the ability to add specific, relevant information to your transactions note that gocardless currently supports up to three key value pairs per record type this limitation is imposed by gocardless, not unaric payments once processed, the metadata will be visible on the corresponding payment, customer, or mandate object within the gocardless dashboard to add custom metadata to a gocardless payment record navigate to the payment record in salesforce locate the psp passthrough parameters field (if this field is not visible, ask your salesforce administrator to add it to the page layout ) enter the metadata in json format using the "payment metadata" key {"payment metadata" {"key1" "value1", "key2" "value2", "key3" "value3"}} save the payment record to add custom metadata to a gocardless authorisation record (for mandates and customers) locate the psp passthrough parameters field (if this field is not visible, ask your salesforce administrator to add it to the page layout ) navigate to the authorisation record in salesforce locate the psp passthrough parameters field (if this field is not visible, ask your salesforce administrator to add it to the page layout ) enter the metadata in json format using the customer metadata and/or mandate metadata keys {"customer metadata" {"customerkey1" "customervalue1", "customerkey2" "customervalue2"}, "mandate metadata" {"mandatekey1" "mandatevalue1", "mandatekey2" "mandatevalue2"}} save the authorisation record sagepay sagepay supports sending a reference for payment records using a single "reference" key,, known as the vendordata parameter in their documentation example {"reference" "testref"} this field accepts up to 200 alphanumeric characters and appears in the sagepay dashboard under the "reference" column avoid special characters like underscores in the reference, as they will cause payment failures you can also specify per transaction financial institution (6012) data for details, see docid 7dhvg xydkp1xngmfa03n