All the payment methods not returning in BigCommerce Get Accepted Payment method rest api - bigcommerce

I am using BigCommerce Rest API in my React Native application to create an eCommerce app for a BigCommerce site. I am doing all the functionalities like getting products, creating a cart, creating checkout, etc, using BigCommerce rest API.
Now, there is an API to get all the accepted payment methods for checkout.
Api : https://developer.bigcommerce.com/api-reference/store-management/payment-processing/accepted-methods/paymentsmethodsget
So, when I am calling this API with all the required parameters and headers, I am getting only one payment method in the response. However, I have set up many other payment method options from the admin.
There is another API Get All Payment method, which returns all the payment methods that I have set up. But returned payment method data does not contain payment method id. I need a payment method id to pass it on next step.
Please anyone knows how to get all the accepted payment methods with it's id in BigCommerce rest API?

It's to my belief that this is working as expected. The v3/payments/methods returns only a list of providers that are supported by our public payments api. This list does not include COD, so that's why that one is missing. You likely don’t see Paypal because it is Paypal Commerce Platform, which is also not expected to be returned.
As a note, this endpoint is tied to an order so if certain providers have restrictions on order total or products or things like that, they might appear/or not appear depending on those values.

Related

Shopify APIs - creating order without receiving payment from end-user

So we're building a buy-now-pay-later store module in our web-app that will be integrated into Shopify (via Shopify's Storefront APIs).
Our users should be able to make orders through our web app (without payment), and then someone on our end will be able to fulfill the order.
The user would then able to make their payment after the fact (via a custom payment implementation handled on our side), and then a webhook would just update the payment status from 'Pending Payment' to 'Complete' on shopify.
Is this possible via Shopify's APIs? We're trying to find a way to directly create an order without requiring payment, but our devs aren't having that much luck.
It is very much easy to do when you work with Draft Orders. That allows you to create a comprehensive near perfect order in the store. The main advantage is, you get define the payment using API calls. So you can convert this Draft Order to a real one, requiring a payment, when you wish to actually charge the customer, and you do that with code. They are sent an email with a link to a real checkout, allowing them to actually pay. You can also convert the Draft Order to a real order, without sending the customer the generated link to make a payment, and therefore, you can fulfill a real Order in the store, and get the customer to pay later, when you wish.

Porting from NVP to REST API

I am currently using PayPal's NVP API. And using the below methods.
TransactionSearch (To pull in historic and recent transactions)
GetTransactionDetails (To fetch detail for each transaction)
TransactionSearch using PROFILEID (To get subscription/recurring transactions related to a particular subscription/recurring profile using the Subscription/Profile ID)
RefundTransaction (To refund a transaction)
ManageSubscriptions (To manage - cancel, suspend, reactivate a particular subscription using the Recurring/Subscription/Profile ID)
GetBalance (To get balance for a particular account)
MassPay (To send money to other PayPal accounts using the email address) I would like to know and get assured that I won't be missing anything when I port to REST, and will get all the details (including all the fields) that I have been getting from the NVP response.
Question 1
Can you map me to the respective REST methods for the above 7 cases that I have listed?
Question 2
Can I use the same credentials for REST API? Or do I need to use something else? Doing so will require the users to reconnect to my system via some other method?
Question 3
Another thing I wanted to know is, that if the REST API can be used to pull in historic data(data for all date ranges)? Is there any restriction on the user-type or type of PayPal account or date-ranges or anything else when using the REST API?
Question 4
What else do I need to take care of when I port from NVP to REST?
Please help!

How does one associate a website user with a Paypal subscription?

I am implementing subscriptions to a premium service on a website using Paypal as the payment service. I have successfully created a Catalog Product and Billing Plan through the API, and I am able to get to the payment page on Paypal, but it's not clear how I'm supposed to persist a user identifier through the purchase process.
I assumed it would be something along the lines of passing a user id somewhere, but there's nothing in the Paypal documentation about this. I need to be able to let the user make a purchase and have the Paypal webhook send the confirmation to an endpoint on my site, and that's where I'd expect to get their user id to toggle the subscription on their account on my end.
Is there something I'm missing? There has to be a way to do this cause I'd imagine it's a pretty common use case. If anyone has information or has done this before, I'd love to hear. Thanks.
The only truly secure way I've found when using javascript SDK, is to securely generate a unique custom_id on your server side associated with the user.
Then when you create the buttons, the 'createSubscription' function takes custom_id as a parameter.
Then use a webhook to receive events from your subscription and the custom_id will be present in the body of all BILLING.SUBSCRIPTION events under resource.custom_id.
I am able to get to the payment page on PayPal,
You are vague about what you are doing here. There are multiple ways (and some ways have multiple versions) of accepting subscriptions via PayPal, so it is important that you provide full details about the method you are using.
The time to associate a created subscription ID with a user ID is when it is approved, in the onApprove function if you are using a Smart Payment Button: https://developer.paypal.com/docs/subscriptions/integrate/#4-create-a-subscription

how to access shopify Products via API without api-key and password?

i want to develop a chrome extension to see stats for any store which develop in shopify, can i access any store products without API-Key and Password in shopify?
No, you cant access products json without using api-key or permanent token of the store.
But still you want to access the product details you atleast needs the handler of the product.
Lets say your store is "abc.myshopify.com" and handler of your product is "xyz", then you can product json of xyz by HTTP GET call in following url
https://www.abc.myshopify.com/products/xyz.json
in general
https://www.[storename]/products/[product-handle].json
You could try using the Shopify StoreFront API.
It allows to get information of your shop from from your own website or custom app. Although it doesn't need a API Password, it needs a Api Key that doesn't need to be a secret.
The documentation says this (the first point is the important):
Using the Storefront API, you can:
Fetch data about a single product or a collection of products to
display on any website or device.
Create unique checkout experiences
with full control over the shopping cart.
Create new customers or
modify existing ones, including address information.
Allow customers
to select unique product options.
There is no way shopify will provide store details (product list) without api authentication.
For your requirement, I would suggest to create a shopify app which will sync all product details to your storage and you can access data from there.

Access Shopify Property via post request

I want to access the shopify api object to get (paymentMethod , paymentReference , refundedAmount and risklevel).
How can I?
Connect to the shop using the API, and ask for the order(s) of interest. All the payment information for order is available either with the order itself, or by asking for the transactions belonging to the order. All clearly documented in the API documentation.