Is there any way for validating paypal cardnumber before starting payment process?
Now,my paypal payment will work only if cardnumber is 16 digit.
suppose if i enter 14 digit number,it show error like this :
cardnumber invalid
This is not any response from paypal.is there anyway for validating card number before payment process start?
Related
I have a case when SFMC JB performed an SMS send to records, that did not have a phone number in DE for Entry Source, but there is a phone number assigned to them in the database.
The Journey settings were set to "Use phone number attribute from entry source - Phone".
Here is an example record in DE:
SubscriberKey | Email | Phone
123 | example#gmail.com | null
Help states that "To send SMS from a journey, the normalized phone number (country code + phone number with no dashes or parentheses) is required in your data extension."
Could you please tell me how to troubleshoot this case, or if you see any other potential things that have given the following output? And how to perform a send so it does not happen again?
Thanks a lot!
We're building a marketplace in NEAR. We have two smart contracts for token and marketplace. Same as NEAR example.
In our platform, we have successfully implemented below features:
Token mint (used contract method: nft_mint)
Token listing for sale in marketplace (used contract methods: storage_deposit nft_approve)
Token purchase (used contract method: offer)
Everything is working fine.
Now, we want to charge the transaction fee (2.5%) on each sales for our marketplace.
--
I did one mint and buy test with Paras Marketplace to observe the royalty and transaction fee distribution. Here is the test details:
With seller.near account, I minted an NFT in Paras Marketplace. And added 3% royalty. And listed it #1 Ⓝ for sale.
With buyer.near account, bought it with another account.
NFT Details:
Name : My Non-fungible token #1
Listed Price : 1 Ⓝ
Royalty : 3%
Sale Breakdown:
Receive (Seller) : 0.95 Ⓝ
Royalty (Creator) : 0.03 Ⓝ
Fee (Paras) : 0.02 Ⓝ
Before purchase - Account Balance
buyer.near : 50.03995 Ⓝ
seller.near : 4.896 Ⓝ
After purchase (1st sale after minted) - Account Balance
buyer.near : 49.03388 Ⓝ | Difference : -1.00607 Ⓝ
seller.near : 5.82587 Ⓝ | Difference : +0.92987 Ⓝ
# NFT Create Transaction
This is nft_create_series transaction. Where Paras is sending "transaction_fee": "200" to charge 2% service fee on each sale:
# NFT Buy Transaction
This is buy transaction. Where Paras charged 2% service fee:
Question:
We want to charge 2.5% service fee on each sales.
We want to implement "transaction_fee": "250" object in our marketplace contract.
How to do the same with our marketplace?
There are several ways that you can go about doing this. The two that I would recommend are the following (I saw you were following along with the zero to hero tutorial):
Option A (simplest) - store your account in the perpetual royalties object for the token when it is minted.
This is the easiest to implement as you don't need to change anything in your contracts and you simply need to alter what is passed into the royalties object on mint.
This requires that you have control over the NFT contract.
This allows you to receive royalties on whatever marketplace the token is sold on since the royalties are stored on the token level in the NFT contract.
This allows you to specify which account should receive the royalties instead of forcing the marketplace contract to store the funds.
Option B - before calling nft_transfer_payout in your marketplace contract, subtract 2.5% from the price object. This will result in your marketplace contract keeping the 2.5% and paying out the remaining 97.5% to the respective accounts.
With this approach, since many accounts are paying for storage, your contract has funds that aren't all withdraw-able by you. You should keep a tally on how much $NEAR you've received so that you can withdraw that amount and not accidentally withdraw too many funds that may have "belonged" to someone else via storage deposits.
I am trying to create a chatbot for booking flight tickets in watson assistant. The problem is that I want to enable the slot of return_date only when the trip is a roundtrip. But on testing the bot the context variable of $return_date is not getting reflected where as the $start_date is getting updated with the value of sys-date entered when prompted for return_date.
pic 1
pic 2
Also when trying if the user enters "I want to book roundtrip tickets for 4 people in economy class" then the bot asks for the remaining slot values but does not invoke the slot asking for the return date even though the trip type is mentioned in the conversation.
pic 3
pic 4
pic 5
Please suggest whether the flow needs to be changed or changes in the JSON editor will solve this problem.
I am getting transaction declined errors (The transaction was Declined (BH)) when using a test with DPS Payment Express account (PxPay 2.0) for processing credit cards on a website.I am using test credit card no 4111111111111111, expiry date is any future date ,any name for card holder name and 3 digit csv numer.
I am getting following error(response)
Response:DECLINED
Response Code:BH
Currency:USD
Amount: 2016.92
Card:411111........11
Card Holder:MANISH KUMAR
Card Type:Visa
Date:20141007
Time:060747
Transaction Type:Purchase
Help Text:The transaction was Declined (BH)
Can any one please help me....
It is solved by change the currency to NZD.
For others that are using PXPOST "The transaction was Declined (BH)" means that the port is not configured for the Currency you are trying to charge in.
In our case we already had a multi-currency merchant account with our bank but we had to call Payment Express and ask them to enable the new currency we were sending.
I have magento 1.8 with a 1.7 ves_t-shirt theme installed.
I have Swift Checkout and onestepcheckout
The problem is that after hitting “Purchase” the credit card data is getting posted twice.
payment[cc_cid] 567
payment[cc_cid]
payment[cc_exp_month] 6
payment[cc_exp_year] 2016
payment[cc_number] 4111111111111
payment[cc_number]
payment[cc_type] VI
payment[method] braintree
this is the post data from firebug. You can see that the CID and CC# are being posted twice. The second is blank which then triggers this error:
There was an error capturing the transaction. (Transaction declined: Credit card number is required. Credit card must include either number or venmo_sdk_payment_method_code. Credit card type is not accepted by this merchant account.)
Can anyone tell me how to stop the second set of data?