...
A - It's a fail safe to prevent double payment transactions being created (i.e overcharging an opportunity). If you click the "Process Payment" button again it will display a "Payment Source is already processed in the Gateway. Please refer to Process Payment Debug Logs."
| View file | ||||
|---|---|---|---|---|
|
| View file | ||||
|---|---|---|---|---|
|
Q - How do I work out what payments will be processed today?
...
Q - Why does the Pronto Payments Settings Page format look weird?
| View file | ||||
|---|---|---|---|---|
|
A - This is most likely a result of two separate users simultaneously using different "Modes" - i.e Lightning and Classic. To resolve this, switch to the other "mode" and then try accessing the settings page after.
...
Scroll down to the Inactive Values list and 'Activate' the Refunded stage.
| View file | ||||
|---|---|---|---|---|
|
This stage will now be available for reporting.
...
A - It is not possible to edit the PP Payment Batch from within Salesforce UI when the status is closed, however, you may use the data loader to update(ex: name field) the information of the record.
| View file | ||||
|---|---|---|---|---|
|
Q - Which Gateways require CVV to process payment?
...
A: This is a Gateway limitation. Please note that credit card surcharges for large transactions are really high and could be hundreds of dollars, thus the recommended method for large amounts is either bank transfer or cheque. If you want to persist in charging via credit card, you will have to break up the amount to 10,000 over several days, as the gateways will not allow you to charge the same payment source multiple times in a day.
Q: We are required to renew the REST API Key for our Payway, as the current key is set to expire on December 14th. I possess the new API key but encountered an issue while attempting to update it, specifically with the ASPHPP.ASPP_TriggerHandlerGateway [94,1] Apex stack.
A: The issue was found when the client updated the API Token of the gateway. The trigger executes on that update and it runs a query search to the payment transaction object. It checks if the updated gateway has open transactions linked to it. If true, PP will not allow the changes otherwise proceed. Though technically, ProntoPayments only queries 1 record (see code below) salesforce performs table scans internally.
...
The client’s org has more than 2M records so when salesforce runs the table scan it reaches the limit of the final threshold - 600k. GuideDogs has more than 600k+ thus making the query unselective.
...
To make the query passable and successfully update the Gateway API key, you need to contact Salesforce and request to Index the possible fields inside the query (e.g. Payment Status).
Note: Here’s a /wiki/spaces/POSINT/pages/33030212on how to log a Salesforce Support Request.