--- title: "Payments FAQ" slug: "payments-faq" tags: ["Payments"] updated: 2024-08-14T16:15:05Z published: 2024-08-14T16:15:05Z canonical: "docs.blackthorn.io/payments-faq" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.blackthorn.io/llms.txt > Use this file to discover all available pages before exploring further. # Payments FAQ If you still have questions after looking through our Troubleshooting documentation please contact [Blackthorn Support](https://community.blackthorn.io/s/support). We're happy to help! ## Payment Gateways ### Set Up a Payment Gateway for a Newly Acquired Company What are the best practices for setting up a Payment Gateway for a company we've recently acquired? We suggest creating a new Stripe account and a new Payment Gateway for your newly acquired company. From Blackthorn's end, we can support two gateways - one for each company. To learn more about creating and managing multiple Stripe accounts, click [here](https://stripe.com/docs/account/multiple-accounts#:~:text=Separate%20tax%20and%20legal%20entity,create%20additional%20accounts%20for%20each). If you have more Stripe-specific questions, please reach out to Stripe support. ### Spreedly and the Payment Gateway Customer record Why isn’t a Payment Gateway Customer record created when I add a Payment Method via the Virtual Terminal with Spreedly as the Payment Gateway? Since Spreedly does not have an equivalent record (ex. user id) for customers, a Payment Gateway Customer record will not be created in Salesforce. ## Virtual Terminal ### Blocked by Content Security Policy error on Virtual terminal ![I_02_troubleshooting 1](https://cdn.document360.io/f977eec0-500f-40a3-b663-724a51f78075/Images/Documentation/I_02_troubleshooting%201.png) Follow step 4 in [this guide](/v1/docs/quick-start) to ensure your domain is allowlisted. ### Can't See the Related To Field on the Virtual Terminal Why can't I see the **Related To** field on the Virtual Terminal? The reason you cannot see the **Related To** field is that there is an issue with your Transaction Parent settings. Please navigate to Custom Settings, click manage next to Transaction Parents, verify that all records have a Transaction field with the correct API format. ### Can't See the BT Payments LWC Virtual Terminal in the Experience Cloud Builder I can’t see the BT Payments LWC Virtual Terminal component in the Experience Cloud Builder. How do I fix that? If an Experience Cloud user cannot see the BT Payments LWC Virtual Terminal component, please verify the following. - The digital experience user has a Payment License, if in production. - The user has been assigned the correct permission set(s). ## Transactions ### Remove a Transaction Parent Object How do I remove a Transaction parent object? Please see our [Transaction](/v1/docs/transactions) documentation. ### Update Scheduled Transactions If the user who installed Blackthorn Payments is no longer active, schedule jobs will fail. Those jobs include capturing Transactions and Webhook Services. 1. Navigate to Schedule Jobs. - *Lightning/Classic: Setup | In the Quick Find/Search type in and click "Scheduled Jobs".* 2. Click "Del" next to Blackthorn | Payments Daily Captures. 3. Navigate to Apex Classes. - *Lightning/Classic: Setup | In the Quick Find/Search type in and click "Apex Classes"*. 4. Click the **Schedule Apex** button. 5. Job Name: "Blackthorn | Payments Daily Captures" 6. Apex Class: Select "Transaction_Scheduler" 7. Apex Execution: Select "Weekly" | Check "Sunday-Saturday" | Start = Today's Date | End = As far out as possible | Preferred Start Time = 1:00AM 8. Click Save. ## Stripe ### Stripe Sync Job Keeps Running When you sync the gateway data the sync job keeps running even after hours. The sync job keeps on restarting as long there are Stripe customers found. To solve the issue: - Use the filter to sync with dates ![I_02_troubleshooting 5](https://cdn.document360.io/f977eec0-500f-40a3-b663-724a51f78075/Images/Documentation/I_02_troubleshooting%205.png) - Once the job is done syncing for the defined dates, it'll show as completed. ### Invoice Button Isn't Working Why isn’t the **Send Invoice** button on the Invoice object sending the Invoice to the customer? Clicking the button sends the Invoice from Stripe, and Stripe’s [email settings](https://docs.stripe.com/invoicing/send-email) control the process. If you don’t see an email, it may be an issue with your Stripe email settings or a restriction on Stripe’s side that is preventing emails from being sent for test mode Invoice s. ### Prevent the Invoice from Being Sent Immediately How do we prevent the Invoice **Status** from changing to “Sent” immediately after the Invoice is pushed to Stripe from Salesforce? To stop the Invoice **Status** from changing to “Sent” immediately after creating and pushing it to Stripe, you must disable the **Disable Send Invoice Immediately** custom setting. Complete the following steps to disable the custom setting. 1. Go to Setup. 2. In the Quick Find box, search for and click “custom settings.” 3. Click **Manage** next to Blackthorn Pay - Trigger Settings. 4. Click **Edit**. 5. Set **Disable Send Invoice Immediately** = “True” (checked). 6. Click **Save**. ## Remove a Payment Method Parent Object How do I remove Payment Method parent object? Please see our [Payment Methods](/v1/docs/payment-methods) documentation. ## Unable to see Payment Objects in the Experience Cloud If the digital experience user is unable to see the payment object (Example - Invoice) in the Experience Cloud, please verify the following. 1. The user has a Payments License (If production). 2. The user has assigned Blackthorn | Payments (Community/Platform User) permission set assigned. 3. The organization-wide default for Payment Gateway = "Public Read-Only." ## Updating Webhook Record Cleanup 1. Navigate to Schedule Jobs. - *Lightning/Classic: Setup | In the Quick Find/Search type in and click "Scheduled Jobs".* 2. Click "Del" next to Blackthorn | Payments Webhook Record Cleanup. 3. Navigate to Apex Classes - *Lightning/Classic: Setup | In the Quick Find/Search type in and click "Apex Classes".* 4. Click the **Schedule Apex** button. 5. Job Name: "Blackthorn | Payments Webhook Record Cleanup" 6. Apex Class: Select "WebhookCleanupJob_Scheduler" 7. Apex Execution: Select "Weekly" | Check "Sunday-Saturday" | Start = Today's Date | End = As far out as possible | Preferred Start Time = 1:00AM 8. Click Save. ## Update Checkout Payment Screen Can I update the Attendee-related fields on the payment screen's page layout? No, the payment screen's page layout can't be configured because the selected Payment Gateway automatically formats it. ## Deactivating a User who Activated Scheduled Jobs 1. Before the original user’s account/profile is deactivated, have a second user perform the following steps. - Go to the Blackthorn | Payments Admin tab. - Click the Scheduled Jobs tab. - Click the **Schedule Recommended Payments Jobs** button and any other relevant buttons on this tab. - Go to the Blackthorn | PayLink Setup Wizard tab. - Click **Grant Access** to authorize PayLink. 2. Remove the original user’s Payments license permission set(s). ## Duplicate Rule References a Missing Matching Rule **Error:** "conference360_Attendee_c.BT_Event_Attendee_Duplicate_Rule: This duplicate rule references a matching rule that doesn't exist. Update the referenced matching rule" If you experience this error message when performing an upgrade, create the following matching and duplicate rule in your org. - Matching Rule Name: BT Events Attendee Matching Rule - API Name: BT_Events_Attendee_Matching_Rule - Description: matched attendee under an event - Matching Criteria : (Attendee: EventEXACTMatchBlank = FALSE) AND (Attendee: Email2EXACTMatchBlank = FALSE) AND (Attendee: First_Name2FUZZY: FIRST NAMEMatchBlank = FALSE) AND (Attendee: Last_Name2FUZZY: LAST NAMEMatchBlank = FALSE) - Duplicate Rule Name: BT Event Attendee Duplicate Rule - API Name: BT_Events_Attendee_Matching_Rule - Record level security: Bypass sharing rules Please make sure the matching rule references the duplicate rule. Once done, try upgrading the app again.