<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://wiki.smarterpay.com/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://wiki.smarterpay.com/feed.php">
        <title>wiki.smarterpay.com - salesforce:legacy:cardpayments</title>
        <description></description>
        <link>https://wiki.smarterpay.com/</link>
        <image rdf:resource="https://wiki.smarterpay.com/_media/wiki/logo.png" />
       <dc:date>2026-05-06T16:32:02+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://wiki.smarterpay.com/salesforce/legacy/cardpayments/architecture?rev=1704294959&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.smarterpay.com/salesforce/legacy/cardpayments/cardpaymentprocess?rev=1704294966&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.smarterpay.com/salesforce/legacy/cardpayments/deferredpayments?rev=1704295011&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.smarterpay.com/salesforce/legacy/cardpayments/refunds?rev=1704294980&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.smarterpay.com/salesforce/legacy/cardpayments/repeatpayments?rev=1704294993&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.smarterpay.com/salesforce/legacy/cardpayments/triggers?rev=1704295027&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://wiki.smarterpay.com/_media/wiki/logo.png">
        <title>wiki.smarterpay.com</title>
        <link>https://wiki.smarterpay.com/</link>
        <url>https://wiki.smarterpay.com/_media/wiki/logo.png</url>
    </image>
    <item rdf:about="https://wiki.smarterpay.com/salesforce/legacy/cardpayments/architecture?rev=1704294959&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-01-03T15:15:59+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Architecture</title>
        <link>https://wiki.smarterpay.com/salesforce/legacy/cardpayments/architecture?rev=1704294959&amp;do=diff</link>
        <description>Architecture



SmarterPay’s Card Payment implementation consists of a set of objects within Salesforce which represent the Card Payment process. These are usually linked to the client&#039;s Account and Contact object with a third object usually linked to a custom object of the clients choosing (Usually a payment or opportunity object).</description>
    </item>
    <item rdf:about="https://wiki.smarterpay.com/salesforce/legacy/cardpayments/cardpaymentprocess?rev=1704294966&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-01-03T15:16:06+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Standard Card Payment Process</title>
        <link>https://wiki.smarterpay.com/salesforce/legacy/cardpayments/cardpaymentprocess?rev=1704294966&amp;do=diff</link>
        <description>Standard Card Payment Process

The process for new card payments is as follows:






Card Payment (Income_Card_Payment__c)

The Card Payment is the master record in terms of SmarterPay’s Card Payment object structure. It holds the bank details, payment details for the Card Payment. It can really be considered a record representation of the card itself.</description>
    </item>
    <item rdf:about="https://wiki.smarterpay.com/salesforce/legacy/cardpayments/deferredpayments?rev=1704295011&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-01-03T15:16:51+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Deferred Payments</title>
        <link>https://wiki.smarterpay.com/salesforce/legacy/cardpayments/deferredpayments?rev=1704295011&amp;do=diff</link>
        <description>Deferred Payments

Sometimes money should not be transferred from a customer straight away, however a card needs to be ‘swiped’ to ensure that funds can be taken at a future point. A typical example of this is for a hotel booking. A hotel may swipe a card and then take any funds after the stay for any additional charges (room service, dining, spa, etc).</description>
    </item>
    <item rdf:about="https://wiki.smarterpay.com/salesforce/legacy/cardpayments/refunds?rev=1704294980&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-01-03T15:16:20+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Refunds</title>
        <link>https://wiki.smarterpay.com/salesforce/legacy/cardpayments/refunds?rev=1704294980&amp;do=diff</link>
        <description>Refunds

Refunds are provided as standard with the SmarterPay card payment installation and can be accessed via the refund button on the Card Payment record.









Refunds produce a Card Payment History record which is tied to the payment. This will detail if the transaction was successful and how much was processed.</description>
    </item>
    <item rdf:about="https://wiki.smarterpay.com/salesforce/legacy/cardpayments/repeatpayments?rev=1704294993&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-01-03T15:16:33+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Repeat Payments</title>
        <link>https://wiki.smarterpay.com/salesforce/legacy/cardpayments/repeatpayments?rev=1704294993&amp;do=diff</link>
        <description>Repeat Payments

Repeat payments are offered as part of the standard SmarterPay package, however the merchant bank must allow the merchant to have ‘continuous authority’ over cards. 

SmarterPay provide a series of choices for recurring payments depending on the scenario:</description>
    </item>
    <item rdf:about="https://wiki.smarterpay.com/salesforce/legacy/cardpayments/triggers?rev=1704295027&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-01-03T15:17:07+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Triggers and After Payment Processing</title>
        <link>https://wiki.smarterpay.com/salesforce/legacy/cardpayments/triggers?rev=1704295027&amp;do=diff</link>
        <description>Triggers and After Payment Processing

The Salesforce platform opens up consumers of the SmarterPay card payment software to seamlessly fit card payments into the rest of their system. As all card payments are reported to Salesforce as records, triggers, workflows, process builders and platform events may be used to automate any additional processing after a transaction has been made. This allows for functionality such as automatic receipt emails or updates to other, non-SmarterPay, records and …</description>
    </item>
</rdf:RDF>
