Author: Sylvia Odhiambo

To apply different prices based on location (i.e. if you’re in the US you get one rate, if you’re in Uganda, you get a different rate) :

Go to Tickets & Fees to create a sample ticket type.

Then go to Form builder > Attendee registration form (with tickets) and create a country field.

Finally, go to Discount Codes Manager and create a discount code and set it to be valid for selected countries only for selected ticket types.

As a prospective attendee, you would go to the website and select your tickets you would like to purchase, fill up the form and enter the discount code in the Apply discount code field. That would give attendee a discounted rate on that ticket type’s purchase.

When a user selects wire transfer, she/he also needs to enter the details of the wire transfer. 

If user does not have the wire transfer details at the time of pacing the order, she/he can still place the order and then come back to Tickets & Invoices under the dashboard, click on Order # and to view the option to update bank transfer details.

If you are receiving Transactions back from Authorize.net with the message “This transaction cannot be accepted“, Reason code 103, it is likely that your Transaction Key has been reset in Authorize.net, and needs to be updated in Dryfta under Tickets & Fees > Payment Settings.

That would resolve the issue.

To sell merchandises, you can create add-ons and enter pricing for each add-on. Users can purchase these add-ons while purchasing the tickets. As of now, one can only purchase add-ons along with tickets and cannot purchase them standalone.

To create an add-on, follow the steps below:

Go to Form builder and click on Attendee registration form (with paid tickets)

Click on Add new field and select Add-on field type.

Enter the name of the merchandise/add-on along with pricing for each add-on. The add-on currency would be the default currency set under payment settings.

The add-ons would now display under the ticket types for which it has been selected. Please note that once an add-on is purchased by one or more users, the add-on cannot be deleted. 

The “Security header is not valid” error message is only caused for two reasons:

Wrong Credentials

Make sure that you’ve put your API Username, API Password and API Signature correctly. 

Sometimes it happens that during copy and paste there is accidentally a space added, this would trigger this error. Double-check this settings in the SDK or in the admin panel of your third party shopping cart.

Wrong Endpoint

This error would come up if you send the data to the wrong endpoint. 

Make sure that you sending the live credentials and data to our live endpoint. 

When you want to test your store make sure that you use our test endpoint and the credentials from your sandbox test account. 

If you are using a third party shopping cart, make sure that your store is running in test or live mode, regarding which credentials you are using.

Here’s how you can check if your credentials are correct:

FOR LIVE

https://api-3t.paypal.com/nvp?&user=xxxxxxxxxx&pwd=xxxxxxxxxx&signature=xxxxxxxxxx&version=70.0&METHOD=SetExpressCheckout&RETURNURL=http://www.paypal.com/test.php&CANCELURL=http://www.paypal.com/test.php&PAYMENTACTION=Sale&AMT=50&CURRENCYCODE=USD

FOR SANDBOX

https://api-3t.sandbox.paypal.com/nvp?&user=xxxxxxxxxx&pwd=xxxxxxxxxx&signature=xxxxxxxxxx&version=70.0&METHOD=SetExpressCheckout&RETURNURL=http://www.paypal.com/test.php&CANCELURL=http://www.paypal.com/test.php&PAYMENTACTION=Sale&AMT=50&CURRENCYCODE=USD

Just Substitute the user, pwd and signature and enter in your browser.You should get ACK = SUCCESS if you have input your credentials correctly.

You can also get your credentials from under your PayPal dashboard : https://www.paypal.com/cgi-bin/webscr?cmd=_get-api-signature&generic-flow=true