Giter Club home page Giter Club logo

apis's Introduction

PayFabric - Connect once and grow infinitely with PayFabric’s simple, yet powerful RESTful API that allows developers to bypass the complexities and PCI challenges that accompany integrated payment processing software.

PayLink - PayLink provides an easy-to-use Web Interface and simple API for secure payment acceptance for both merchant and developers. PayLink also include ERP connectors that allow seamless integration with Microsoft Dynamics GP, SL and SalesPad.

Receivables - PayFabric Receivables is an add-on service to PayFabric that provides businesses the tools to streamline their online bill presentment and payment needs.

apis's People

Contributors

andrewdoriagp avatar arrayent-zz avatar davidgeli avatar drunklils avatar jackiig avatar jessicaji avatar jingjinghu avatar kaycebasques avatar kevinkangp avatar michaeldaighnodus avatar navarr avatar nickdadar avatar nikkipnguyen avatar renawu avatar sgillbank avatar youngkai7 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

apis's Issues

Transactions guide does not convey source of required settings.

While attempting to create an integration, and following these guides:

The required value SetupId is not explained well. The item is bolded to indicate that it is required, but a value is supplied, as if to suggest a viable default value of "PFP". This value took multiple developers hours to find and update.

Suggest updating the documentation to explain where in the PayFabric web UI this value originates from.

User defined fields are lost when changing a Book request to a Ship request

We are doing a pre-auth (Book) request using the hosted page. When the call returns we are getting our user defined values back in the TrxUserDefinedX fields. We then do some processing on our side and try to capture the payment by using the ?trxtype=SHIP endpoint on the Book transaction. When processing completes we get a brand new transaction back. But the new transaction has thrown away all the user-defined fields so we lose the data we had stored.

This may be by design but it introduces problems. Without the user defined data we cannot link the transaction back to our data. Our original plan was to store a unique identifier in these fields that will work its way to the backend processor such that when we got our monthly report from them we have something to compare against our side of the fence for reconciliation like we do in our existing payment system. But without the user defined fields that doesn't seem possible.

Feature Request: Support $0.00 Unit Price on Line Items

For our application, it is possible for documents to have items with $0.00 unit prices - reason being that if a company decided to give an item to a customer for free, they could still have that one item allocated to the document.

We would like to show this item on the document, but with the unit price being $0.00 so the customer knows they're receiving this item for free.

Currently when you try to add an item with a unit price of $0.00, you get an error message saying "Unit Price is invalid" or something along those lines.

Thank you!

Resolution of the TransactionKey value

It appears that in the sandbox the transaction key is simply the date/time (yyMMddhhmmss). Does this mean that I can only generate 1 transaction request per second? What if I have multiple applications running simultaneously and they happen to try to create a transaction at the same time. Will I get potentially duplicate keys?

Missing Functionality/Documentation

Hello,

We would like to use the PaymentProfileId created on a hosted PayFabric wallet management page as an argument to the CreateTransaction and ProcessTransaction API endpoints. We had designed our solution in this way to avoid needing to handle Account Numbers and ABA numbers in our server side code. The other consideration is that our invoice payment code runs via windows service so we cannot use a hosted payment page.

User defined values not coming back as part of transactions

When we create a transaction in Payfabric we are setting one of the user defined fields to a value. When we later get that transaction back the user defined fields are all blank. This limits the usefulness of the user defined fields.

Create Transaction API is not returning key

Hi,

I'm using example code snippet of node.js for Create Transaction but didn't get any key in return from postman.
{
"SetupId" : "PFP",
"Type" : "Sale",
"Customer" : "PayFabric",
"Amount" : 19.99,
"Currency" : "USD",
"Card" : {
"Account" : "4111111145551142",
"ExpDate": "0330",
"CardHolder" : {
"FirstName" : "John",
"LastName" : "Doe"
}
}
}

L2/L3 field documentation is unclear

In the L2/L3 field documentation here the documentation is unclear on some things.

Commodity Code

It mentions that the commodity code is required and that you should refer to the documentation to the right to get the right one for your industry. But there is no actual list given anywhere. Please link to or provide a list of commodity codes that should be used.

Also please consider clarifying whether this is a fixed list that is validated or simply a required field.

Required fields do not line up with UI

In the Gateway Profile UI where you enable L2/L3 fields it provides a list of required fields (and some optional ones) and the tooltip has some basic information. But the UI doesn't line up with the required fields in the docs. For example freight amount is listed as required in the docs but not exposed in the UI. Shipping country is in the UI as required but not listed in the docs. It is unclear whether the documentation is up to date with the UI or not.

Authorization document shows basic auth but it is either incorrect or doesn't work

Because we are using AuthenticationHeaderValue from .NET to authenticate to PayFabric we wanted to use basic auth. The documentation says it should work but it doesn't. I tried in Postman as well.

However the documentation shows 2 different values being used so I'm unclear if there is an issue with the API or the documentation is wrong. In the comments about basic auth it says the format is {DCN}{DeviceId}:{Password} but it doesn't define what DCN is. However in the code example it just uses the device ID and password as I would expect. However trying to do this in Postman generates a 401. I know the info is correct because if I switch over to using the other auth approach it works correctly.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.